Project

General

Profile

Feature #3551

Jenkins plugin

Added by Vadim about 1 year ago. Updated 3 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
RapidDeploy - 5.0-FIX
Start date:
05/22/2020
Due date:
% Done:

0%

Estimated time:
Affects Version:
RapidDeploy - 5.0-FIX
Timesheet Code:
Additional version details:

Description

Hello.

Am working with system "build in Jenkins, deploy in RapidDeploy". Everything works perfectly. Just one thing could do better. :)
Function "rdProjectDeploy", which deploys project directly, without plan, sends all logs to Jenkins pipeline. A lot of information about manifests and other RapidDeploy data. It could be great to have possibility to eliminate full log and get summary information only. As it's done with "rdJobPlanRun" function - it has argument "showFullLogs". Or there could be no argument as in "rdPackageBuild" function. This information is really very specific and is not necessary on each casual deployment.

Thank You in advance!

Best regards,
Vadim.


Files

firefox_3MGUGkprKU.png (40.7 KB) firefox_3MGUGkprKU.png Vadim, 02/22/2021 08:15 PM
firefox_ZThA07ySv6.png (16.9 KB) firefox_ZThA07ySv6.png Vadim, 02/22/2021 08:15 PM
#1

Updated by Rafael about 1 year ago

  • Assignee set to Rafael
  • Target version set to 5.0-FIX

True Vadim, thanks! :-)

I'll put this into our roadmap.

Cheers!

Rafa

#2

Updated by Rafael about 1 year ago

  • Status changed from New to In Progress
#3

Updated by Rafael 12 months ago

  • Status changed from In Progress to Marked for Closure

Hi Vadim,

This feature is finally out! :-)

Just update to the new 4.5 version of the RapidDeploy plugin for Jenkins:

https://plugins.jenkins.io/rapiddeploy-jenkins

Just a little warning: I'm pretty sure you were already calling a RapidDeploy job plan from Jenkins, if this is the case, please check the configuration of the Jenkins job as the "Show Full Logs" checkbox has now a different name and a different purpose.

Let me know if you like it! :-)

And feel free to close this ticket when you test it, otherwise I'll just time it out in a few days time.

Cheers!

Rafa

#4

Updated by Vadim 12 months ago

Hi Rafael.

Great news! Thank You very much! I'll check my codes, update plugin and test it. Will inform You in case of any problems.

Best regards,
Vadim.

#5

Updated by Rafael 11 months ago

  • Assignee changed from Rafael to Vadim
#6

Updated by Vadim 11 months ago

Hi Rafael.

Finally got back to the plugin to update it. But cannot find any description of a new version. :) No changelog also is attached to the plugin. And I cannot see any new code on GitHub. :) Can You please check if it is really released.

Please let me know.

Best regards,
Vadim.

#7

Updated by Rafael 11 months ago

Hi Vadim,

It's true I haven't provided any changelog, when they are small changes and fixes like this I just don't bother, plus, a few months ago they migrated the Jenkins plugin documentation site from the Jenkins Wiki to the GitHub pages, and I haven't done this yet, so I can't really add or modify anything in our Jenkins plugin documentation page:

https://plugins.jenkins.io/rapiddeploy-jenkins

Although in that same page you can see how the last release was the version 4.5, 2 weeks ago.

And also if you check the GitHub plugin site:

https://github.com/jenkinsci/rapiddeploy-plugin/commits/master

You can also see the last commits a couple of weeks ago.

Maybe you checked it somewhere else?

In any case, you should only need to go to the "Plugin Manager" section of the Jenkins administration page and check the "Available updates" tab to see there's a new version of the RapidDeploy plugin.

Anyway, let me know if you have any problem and I'll try to help you!

Cheers!

Rafa

#8

Updated by Vadim 11 months ago

Hi Rafael,

As we discussed through the call, please put some description about the changes in Jenkins plugin from the pipeline side: which parameters were added, which were changed. :)

Thank You!

Best regards,
Vadim.

#9

Updated by Rafael 11 months ago

  • Status changed from Marked for Closure to In Progress
  • Assignee changed from Vadim to Rafael

Hi Vadim,

You're right, I actually didn't make this feature extensible to the Jenkins pipeline option, I need to implement this!

Regarding the documentation of each field, I just realised they are actually described generically in the "Tasks" section right before the "Jenkins Pipeline steps" one:

https://plugins.jenkins.io/rapiddeploy-jenkins

In any case, it would really nice to have an example of each possible pipeline step and a better explanation, and I also need to add a description for the new "Show full log" field though. :-)

Thanks for reminding, leave it on me, I'll keep you posted on any update! :-)

Cheers!

Rafa

#10

Updated by Vadim 9 months ago

Hi Rafael.

You said that controls this. So just want to remember not to forget. :) We were talking about calling RapidDeploy plugin functions from a Jenkins scripted pipeline. RD returns too much logs and makes build log too big and less informative. :)

Please check if it is possible to pass a "Show full logs = False" parameter to a scripted pipeline function as well.

Best regards,
Vadim.

#11

Updated by Rafael 9 months ago

Hi Vadim,

This is still in my list. We had some other urgencies and I didn't have the time to work on this, but I'll keep you updated when we release this feature! :-)

Cheers!

Rafa

#12

Updated by Vadim 8 months ago

Hi Rafael.

Don't You have any update for this my request? :)

Best regards,
Vadim.

#13

Updated by Rafael 8 months ago

Hi Vadim,

It is still in my list, but I haven't had any time to work on this.

I'll keep you posted with any update.

Cheers!

Rafa

#14

Updated by Rafael 4 months ago

Hi Vadim,

As stated in #3725, this feature was finally, after so long, released! :-)

I still need to update the documentation, so I'm leaving the ticket open, but in the meanwhile, this is an example of how you can use the three available steps:

rdPackageBuild serverUrl: "${RD_SERVER_URL}", 
    authToken: "${RD_AUTH_TOKEN}", 
    project: 'CI_Test', 
    packageName: '', 
    archiveExtension: 'zip'
rdProjectDeploy serverUrl: "${RD_SERVER_URL}", 
   authToken: "${RD_AUTH_TOKEN}", 
    project: 'CI_Test', 
    target: 'localhost_linux.dev.LocalTest', 
    deploymentPackageName: 'LATEST', 
    asynchronous: false, 
    showFullLog: false,
    dictionary: ["@@INITIAL_BUILD@@":"${env.INITIAL_BUILD}", "@@ANOTHER_BUILD@@":"10.0.0.3"]
rdJobPlanRun serverUrl: "${RD_SERVER_URL}", 
    authToken: "${RD_AUTH_TOKEN}", 
    jobPlanId: 1, 
    asynchronous: false, 
    showIndividualLogs: true, 
    showFullLog: true

Please let me know if you need further help.

Cheers!

Rafa

#15

Updated by Vadim 4 months ago

Hi Rafael.

Great! I'll do update and check. :) Will let You know in case of any problems.

Best regards,
Vadim.

#16

Updated by Vadim 4 months ago

Hi Rafael.

It works just perfectly! Thank You very much!

Please don't forget to update a description. ;)

Best regards,
Vadim.

#17

Updated by Vadim 4 months ago

Hi again.

Seems that there is some mess up with parameter names. :) rdProjectDeploy function has showFullLog parameter, and rdJobPlanRun has showIndividualLogs and showFullLogs parameters (in accordance to Jenkins logs). Log/Logs... :) Can You please double check this place?

Am attaching Jenkins log screenshot.

Best regards,
Vadim.

#18

Updated by Rafael 4 months ago

Hi Vadim,

I'm glad you like it and find it useful! :-)

Yeah, I have to update the documentation, but all the Jenkins plugins documentation pages have been moved to GitHub to what they call "documentation as code" (https://www.jenkins.io/blog/2019/10/21/plugin-docs-on-github), and I just need more time for it, that's why I'm leaving the ticket open. ;-)

The step parameters are correct, at least that's what I meant, the only difference is that the old "showFullLogs" for the job plan execution step, now is "showIndividualLogs".

The reason why one is plural and the other one singular, at least as I thought it, is because one is "show individual log (file)s" and the other one is "show full log (file)". Otherwise, I think "individual logs" and "full logs" is more prompted to mistakes. I googled it and gave it a deep thought, and just came to this conclusion, but you are right it can lead to some misunderstanding. I hope it is clearer when the documentation is ready! :-)

Thanks so much for all your feedback!

Cheers!

Rafa

#19

Updated by Rafael 4 months ago

Oh! I just realised you had attached screenshots about the parameters!

Yeah, you are right, that is indeed a little mistake when printing the parameters, I'll fix it for the next release.

Thanks a lot! :-)

Cheers!

Rafa

#20

Updated by Rafael 3 months ago

  • Status changed from In Progress to Marked for Closure
  • Assignee changed from Rafael to Vadim

Hi Vadim,

Finally, after so long, the documentation has been updated! :-)

You can check it in the following link:

https://plugins.jenkins.io/rapiddeploy-jenkins

The documentation is now held in the same GitHub repository as the plugin code:

https://github.com/jenkinsci/rapiddeploy-plugin

So feel free to create a pull request if you ever see anything you think should be modified! :-)

I'm going to mark this ticket for closure and close it in a few days time if you don't have any other concern on this regard.

Thanks, one more time, for all your feedback!

Cheers!

Rafa

#21

Updated by Rafael 3 months ago

  • Status changed from Marked for Closure to Closed

Also available in: Atom PDF