RapidDeploy-Community

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.

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.

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

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.

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.

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

Hi Rafael.

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

Best regards,
Vadim.

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

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

Hi Rafael.

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

Best regards,
Vadim.

Hi Rafael.

It works just perfectly! Thank You very much!

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

Best regards,
Vadim.

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

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