Re: Best Way to Sandbox Test Jenkins & Jenkins Plugin Updates?

[Qiang]

We create a docker image with master and latest versions of plugins for 
each upgrade. If the upgrade ends up broken (master itself or pipeline 
jobs), we roll back to the previous image.  Then we can spend time to 
figure out what's wrong (e.g downgrade the bad plugin version), then create 
a new docker image. 
With jenkins docker image, we can also easily provision a staging 
environment (even port the production jobs over) to test the upgrade before 
touching the production. 

Hope that helps :)

On Wednesday, October 10, 2018 at 4:49:28 AM UTC-5, jambih...@gmail.com 
wrote:
>
> Bit of a broad question here... But i run 3 separate Jenkins environments 
> across diff regions on AWS, because I prefer segregation. As my Jenkins 
> servers are tightly locked down, I generally dont need to update 
> continuously but like to do so every 1-2 months at least.
>
> When it comes to Jenkins updates & Jenkins plugin updates, and making sure 
> masters don't break, I have only relied on snapshots. Taking a snap before 
> updating the OS Jenkins version and all plugins If anything breaks, I 
> rollback.
>
> In 2+ years I have not had to rollback until recently. My staging and 
> production Jenkins environments worked fine with the latest updates, but QA 
> failed. This environment has recently added a lot more features & 
> complexity, with additional plugins/services for automated testing and I 
> guess one or more must have broken with the updates.
>
> Oddly, I would normally assume Jenkins itself wouldn't cause things to 
> break, it'd more likely to be plugins which warn of non 
> backwards-compatible changes and the like. However, in this situation, the 
> java ssh process from the master to the slave ceased to work after the 
> updates. I had to specify the actual os ssh process, but then builds had 
> all kinds of errors.
>
> But I digress, after many attempts at downgrading plugins and changing 
> the config, I eventually had to revert to the saved server state for my 
> Jenkins QA master. It would seem the method I've been using to test 
> updates, whilst it does cover screwups and allows me to rollback, is now 
> insufficient for testing for problems beforehand caused by any updates. 
> Obviously having jobs fail to deploy costs valuable time and money, so I 
> need to improve
>
> I'm wondering if anyone has any recommendations for a workflow for testing 
> Jenkins plugin updates for master servers??
>
> I have the slightly annoying issue that I'm using a plugin "SCM Sync 
> Configuration Plugin", to version config changes to github. Any snapshots I 
> take to spinup a new server for testing, immediately cause problems with 
> this for instance -- minor nuisance but this is my point, trying to get a 
> nice automated workflow for testing if any updates are going to break 
> things.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4c281407-734f-4295-b6c8-e2a4534e453e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins docker with NIS user

[Quang Truong]

Hi,

I'm using jenkins docker to spin up a jenkins master, however, we're using 
NIS user to manage the access to jenkins. I have tried to search around but 
I can't see how to integrate the PAM NIS user for jenkins docker. I walk 
through this discussion 

 
about jenkins docker conttainer with AD but not sure how to deal with NIS 
(I have no idea about the mechanism of NIS user too)

Much appreciate on the hints for how to configure with jenkins container

Thanks,
Quang

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/7804f281-b288-4312-ae84-e5eb9097e95b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How can I find the plugin name to use with install-plugins.sh?

[dave.bender]

Is there an API call that could be used to retrieve that and other tidbits 
about the plugin?   We're looking for a way to effectively audit and 
automate our plugin management.  I suppose we could call that page and 
screen scrape the data, but I was wondering if the data displayed is 
already available somewhere. 


Dave


On Friday, September 14, 2018 at 5:04:32 AM UTC-5, Richard Bywater wrote:

> Note that you can also find the ID of a plugin on the plugins.jenkins.io 
> page for that plugin (e.g. https://plugins.jenkins.io/docker-workflow) - 
> its ID is shown just below the plugin name header.
>
> Richard.
>
> On Fri, Sep 14, 2018 at 12:00 AM Thomas Sundberg  > wrote:
>
>> Hi!
>>
>> This is partly answering my own question:
>>
>> Install the plugin you want to try.
>>
>> Run the script
>>
>> Jenkins.instance.pluginManager.plugins.each{
>>   plugin ->
>> println ("${plugin.getDisplayName()} (${plugin.getShortName()}):
>> ${plugin.getVersion()}")
>> }
>>
>> Locate the short name of the plugin you want to deploy and add it to
>> the Dockerfile.
>>
>> In this particular case, look for the line
>>
>> Docker Pipeline (docker-workflow): 1.17
>>
>> and add
>>
>> RUN /usr/local/bin/install-plugins.sh docker-workflow
>>
>> in your Dockerfile.
>>
>> Clumsy? Yes
>> Did it work? Yes
>>
>> What would you like?
>> A section at the page
>> https://wiki.jenkins.io/display/JENKINS/Docker+Pipeline+Plugin stating
>> that the command line name for this plugin is docker-workflow
>>
>> Cheers,
>> Thomas
>>
>> On Thu, 13 Sep 2018 at 13:42, Thomas Sundberg > 
>> wrote:
>> >
>> > Hi!
>> >
>> > I am creating a Jenkins installation from a Dockerfile. I want to
>> > specify all plugins so they are available when the image is built.
>> >
>> > This typically looks like many lines like this:
>> >
>> > RUN /usr/local/bin/install-plugins.sh greenballs
>> >
>> > Is there a way to find the proper name for each plugin? I am currently
>> > looking for the proper name for the Docker Pipeline
>> > Plugin,https://wiki.jenkins.io/display/JENKINS/Docker+Pipeline+Plugin
>> >
>> > Cheers,
>> > Thomas
>> >
>> > --
>> > Thomas Sundberg
>> > M. Sc. in Computer Science
>> >
>> > Mobile: +46 70 767 33 15
>> > Blog: http://www.thinkcode.se/blog
>> > Twitter: @thomassundberg
>> >
>> > Better software through faster feedback
>>
>>
>>
>> --
>> Thomas Sundberg
>> M. Sc. in Computer Science
>>
>> Mobile: +46 70 767 33 15
>> Blog: http://www.thinkcode.se/blog
>> Twitter: @thomassundberg
>>
>> Better software through faster feedback
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/CACpkv-x3VCcC8sWiDqMT%2BDUpPej09cZL7aKXQYQ20zjzENMoxQ%40mail.gmail.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a7868849-5c56-4c32-af6d-d68bb74e4b16%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Programmatically find security advisories by plugin identifier

[dave.bender]

Is there an API or URL or something we could call via a script to get 
current or recent security advisories by plugin shortName or other 
identifier? 

We're trying to automate a means to keep our plugins current or at least be 
able to get alerts on vulnerabilities in plugins used by specific Jobs. 

Does such a thing already exist, or is there programmatic access to the 
topic of the advisories? 


Dave

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/114d96d5-d05b-4bb2-99e9-64b75e6a84e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

call pzinskey (pega) file from jenkins and execute the unit test suites

[panneerrselvam natarajan]

Hi All,

I need to integrate the Unit Test cases using Jenkins, They will provide 
the pzinskey (pega) which containts the list of test suites. I need to 
execute whether pass or fail and provide the result.

Please can i have any suggestion on this.


Regards
Panneer

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ea82d78d-e86f-422c-8a98-fb2dedef9cc2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline bat stdout redirection

[JAY D SHAH]

I am Facing the same issue, Does anyone got something on it

For me, Std_err gets called by Clean_up With Jenkins file due to which I 
can't get the correct error message

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/820a6e00-202f-49c1-8f08-044f31edc95f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Best Way to Sandbox Test Jenkins & Jenkins Plugin Updates?

[jambihosting]

Bit of a broad question here... But i run 3 separate Jenkins environments 
across diff regions on AWS, because I prefer segregation. As my Jenkins 
servers are tightly locked down, I generally dont need to update 
continuously but like to do so every 1-2 months at least.

When it comes to Jenkins updates & Jenkins plugin updates, and making sure 
masters don't break, I have only relied on snapshots. Taking a snap before 
updating the OS Jenkins version and all plugins If anything breaks, I 
rollback.

In 2+ years I have not had to rollback until recently. My staging and 
production Jenkins environments worked fine with the latest updates, but QA 
failed. This environment has recently added a lot more features & 
complexity, with additional plugins/services for automated testing and I 
guess one or more must have broken with the updates.

Oddly, I would normally assume Jenkins itself wouldn't cause things to 
break, it'd more likely to be plugins which warn of non 
backwards-compatible changes and the like. However, in this situation, the 
java ssh process from the master to the slave ceased to work after the 
updates. I had to specify the actual os ssh process, but then builds had 
all kinds of errors.

But I digress, after many attempts at downgrading plugins and changing 
the config, I eventually had to revert to the saved server state for my 
Jenkins QA master. It would seem the method I've been using to test 
updates, whilst it does cover screwups and allows me to rollback, is now 
insufficient for testing for problems beforehand caused by any updates. 
Obviously having jobs fail to deploy costs valuable time and money, so I 
need to improve

I'm wondering if anyone has any recommendations for a workflow for testing 
Jenkins plugin updates for master servers??

I have the slightly annoying issue that I'm using a plugin "SCM Sync 
Configuration Plugin", to version config changes to github. Any snapshots I 
take to spinup a new server for testing, immediately cause problems with 
this for instance -- minor nuisance but this is my point, trying to get a 
nice automated workflow for testing if any updates are going to break 
things.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ff1ab626-74cb-4f32-8dfc-6e2b41308772%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Installing Artifactory and Blue Ocean plugins offline

[Stuart Rowe]

Does anyone know if juseppe works with an existing artifactory instance?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/896a5023-c076-4130-94a1-0da96f5debd9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.