Re: Remote trigger configuration

[Ramanathan Muthaiah]

> I am not able to configure the jenkins for remote trigger. Few years back 
> I had done this, with older version using "Manage Credentials" option. But 
> the latest versions don't have Manage Credentials option to configure 
> hostname, hostname and port, etc options. And the docs in internet/google 
> point to older documents which tell to configure with "Manage Credentials" 
> only. Please help me on this.
>

Are you looking to do remote trigger the build for a particular project / 
job setup in Jenkins ?
If so, then look for "Trigger build remotely (e.g. scripts)" in the job 
configuration.
Remember this will expect you to pass the token of the user.

/Ram 

-- 
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/a4012caf-28e1-4451-b534-67c7420f5df6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Offline upgrade considerations from 1.x to 2.x

[Daniel Beck]

> On 25.12.2016, at 22:27, Jeff  wrote:
> 
> external internet sites

Could you host your own update site internally, possibly firewalled to only 
allow access from that specific Jenkins master?

E.g. https://github.com/yandex-qatools/juseppe

-- 
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/F1ED045E-C286-4841-8C81-2F1165A72C8A%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Offline upgrade considerations from 1.x to 2.x

[Jeff]

I am unable to do this method.  The powers that be won't allow any machine
with source code or access to source code direct access to any external
internet sites.  It took 3 months just to get approval to allow Jenkins to
send build status emails to an internal server, but only after the Jenkins
Master was locked down even further.


On Sun, Dec 25, 2016 at 12:51 PM, Baptiste Mathus  wrote:

> IIUC what you say. No. Don't install a clean one and drop it, that will
> overwrite existing files and probably just screw up everything.
>
> But what you say makes me think of an intermediate way: you can use the
> typical process to move a master to another machine, but then kind of "move
> it back".
>
> Roughly:
> 1. Set up a server with Internet access
> 2. Stop the old server
> 3. Copy things from the existing one to the Internet ready one
> 4.  Upgrade it following the standard docs
> 5. Move it back (rsync --delete)
>
> Search the list about it. There's been plenty of discussions about it.
>
> BTW makes me think we should create a page about that on jenkins.io (if
> there is not already one)
>
> HTH
>
> Le 22 déc. 2016 4:37 PM, "Jeff"  a écrit :
>
> Our Jenkins build server is in a secure (no internet) environment and I'd
> like to upgrade it.
>
> Can I install a clean 2.0 with all the plugins (from outside) and then
> just zip it up, transfer the archive and extract it over the top of the 1.x
> folder structure (except for the jobs/config.xml) along with dropping in a
> new .WAR?
>
> Or are there other considerations I need to be aware of?  I haven't found
> much relating to the upgrade process for this type of scenario.
>
> Thanks.
>
> --
> 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/ms
> gid/jenkinsci-users/CAPJK9%3D%2Bih2XFM0CQOzQBN6_4hxKoCR3Ss7r
> 2BkbA6Vtt5%3Dc9kw%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/CANWgJS7w2kRQKxmDDxz7mVcXXDG4B
> cD5NccSjM36Mp4uVHotJw%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/CAPJK9%3DLbg79GeYfEkHMqK-Pex1DFWDka%2Be4xYiqCeq-5XjSYuA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Offline upgrade considerations from 1.x to 2.x

[Baptiste Mathus]

IIUC what you say. No. Don't install a clean one and drop it, that will
overwrite existing files and probably just screw up everything.

But what you say makes me think of an intermediate way: you can use the
typical process to move a master to another machine, but then kind of "move
it back".

Roughly:
1. Set up a server with Internet access
2. Stop the old server
3. Copy things from the existing one to the Internet ready one
4.  Upgrade it following the standard docs
5. Move it back (rsync --delete)

Search the list about it. There's been plenty of discussions about it.

BTW makes me think we should create a page about that on jenkins.io (if
there is not already one)

HTH

Le 22 déc. 2016 4:37 PM, "Jeff"  a écrit :

Our Jenkins build server is in a secure (no internet) environment and I'd
like to upgrade it.

Can I install a clean 2.0 with all the plugins (from outside) and then just
zip it up, transfer the archive and extract it over the top of the 1.x
folder structure (except for the jobs/config.xml) along with dropping in a
new .WAR?

Or are there other considerations I need to be aware of?  I haven't found
much relating to the upgrade process for this type of scenario.

Thanks.

-- 
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/CAPJK9%3D%2Bih2XFM0CQOzQBN6_
4hxKoCR3Ss7r2BkbA6Vtt5%3Dc9kw%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/CANWgJS7w2kRQKxmDDxz7mVcXXDG4BcD5NccSjM36Mp4uVHotJw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins hangs after upgrade

[Baptiste Mathus]

Hello,

IMO tbh you're mostly on your own here. I mean the initial research,
narrowing down the issue. That because probably only a handful or less of
people both run their master on Solaris and follow the list here...

Having done that in the past for an AIX specific issue: Identify the exact
version of Jenkins where the issue got introduced.

* Use dichotomy for that. Like try the version in the middle of the
[not-working; working] range
* Iterate until finding the right version

Note: if you're using and know git a bit. You can also directly go to
building the sources yourself. And use git bisect to do that in a more
autopilot way.

* Then file a bug report about that specific issue.

Alternatively/complementarily (but it's obvious anyone already has done
that before upgrading): carefully review the changelog for things that may
appear related.

HTH

-- Baptiste


Le 22 déc. 2016 10:11 AM, "John Zhang"  a écrit :

> There is a NullPointerException actually: (The Jenkins is running on
> Solaris 11)
>
> JNA: Callback org.jvnet.solaris.libzfs.ZFSObject$2@15842f threw the
> following exception:
> java.lang.NullPointerException
> at org.jvnet.solaris.libzfs.ZFSObject.create(ZFSObject.java:67)
> at org.jvnet.solaris.libzfs.ZFSObject$2.callback(ZFSObject.
> java:275)
> at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
> thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
>
>
>
> On Thursday, December 22, 2016 at 10:05:41 AM UTC+1, John Zhang wrote:
>>
>> I upgraded my jenkins yesterday and after that, I cannot connect to it by
>> web.
>>
>> I tried to start my Jenkins manually by:
>> java -version:1.7* -jar jenkins.war --prefix=/jenkins
>>
>> I got the following console output:
>>
>> Running from: /apps/jenkins/webapp/jenkins.war
>> webroot: $user.home/.jenkins
>> Dec 22, 2016 9:03:45 AM winstone.Logger logInternal
>> INFO: Beginning extraction from war file
>> Dec 22, 2016 9:03:45 AM org.eclipse.jetty.util.log.JavaUtilLog info
>> INFO: jetty-8.y.z-SNAPSHOT
>> Dec 22, 2016 9:03:48 AM org.eclipse.jetty.util.log.JavaUtilLog info
>> INFO: NO JSP Support for /jenkins, did not find
>> org.apache.jasper.servlet.JspServlet
>> Jenkins home directory: /home/acqop/.jenkins found at: $user.home/.jenkins
>> Dec 22, 2016 9:03:48 AM org.eclipse.jetty.util.log.JavaUtilLog info
>> INFO: Started SelectChannelConnector@0.0.0.0:8080
>> Dec 22, 2016 9:03:48 AM winstone.Logger logInternal
>> INFO: Winstone Servlet Engine v2.0 running: controlPort=disabled
>> Dec 22, 2016 9:03:49 AM jenkins.InitReactorRunner$1 onAttained
>> INFO: Started initialization
>> Dec 22, 2016 9:03:49 AM jenkins.InitReactorRunner$1 onAttained
>> INFO: Listed all plugins
>> Dec 22, 2016 9:03:49 AM jenkins.InitReactorRunner$1 onAttained
>> INFO: Prepared all plugins
>> Dec 22, 2016 9:03:49 AM jenkins.InitReactorRunner$1 onAttained
>> INFO: Started all plugins
>> Dec 22, 2016 9:03:49 AM jenkins.InitReactorRunner$1 onAttained
>> INFO: Augmented all extensions
>> Dec 22, 2016 9:03:49 AM jenkins.InitReactorRunner$1 onAttained
>> INFO: Loaded all jobs
>>
>> So, I cannot find anything abnormal.
>>
>> Any hints what could be the problem and how to trouble shoot?
>>
>> John
>>
>> --
> 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/ms
> gid/jenkinsci-users/9a752604-e9b1-489c-ad97-716b4ffeaff9%
> 40googlegroups.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/CANWgJS7wc5nK%3DEtLH20%2BaMqVqGPfxhSmGfHkwrFSrON%3DGZ_DaA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trouble using shared pipeline libraries

[Ramanathan Muthaiah]

Here are some details but am not confident about my setup based on what 
you're asking.
Maybe, you can help me to clarify what am doing incorrectly. 

* how does your Jenkisfile look like
>
[Ram] : Jenkinsfile content is:

buildUtils("git")
 

> * do you have global shared library configured or per folder? 
>
[Ram] : Looks like am missing some configuration here but fail to 
understand what is it from the plugin docs ?
 

> * which version of the shared library do you adress? Is your script 
> available in that version?
>
[Ram] : Am not sure if understood your question. Shared Groovy library 
plugin installed is v2.5
 

> * do you have same script in the internal repo? 
>
[Ram] : Jenkinsfile and vars/buildUtils.groovy are in the same repo 

TIA,
/Ram

-- 
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/74031c7b-1bb2-4ee7-8f8b-e69a331e23ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Automatic JDK installation not working on AIX systems

[Baptiste Mathus]

+1. This is how we did that in the past for AIX.
And anyway, I think you should not use JDK (or maven, or any tool really)
auto install feature for long in general. It's cool and useful for quick
prototyping but probably not a good idea for your production CD/CI cluster.
(If not obvious why: you don't want your builds to start failing because of
any unavailability from where you're downloading from...)

Le 20 déc. 2016 4:25 PM, "Daniel Beck"  a écrit :

>
> > On 20.12.2016, at 15:11, sunnymarc1...@gmail.com wrote:
> >
> > Is it possible to get AIX systems supported in the near future?
>
> Probably not, unless you do this yourself.
>
> FWIW you could choose to install the JDK from a zip/tar file that Jenkins
> downloads for that machine (limit the install to specific nodes using the
> label expression). While less convenient (it requires preparation by you),
> this should work on all platforms.
>
> --
> 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/AA3BEBED-10BA-4F93-9D71-46A748C888C1%40beckweb.net.
> 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/CANWgJS72ndmUTUQ_UyHRMgT5wX_ag%3Dghm7jjeXtqsLHxfd-Biw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: Hos to test them locally

[Torsten Reinhard]

Hi, 

we were also wondering why there´s that pipeline-as-code approach available 
and strongly recommended everywhere - without any traditional support 
(automated tests) of developing clean code for it.

So we worked around that by doing the following:
- we have a Test Jenkins instance running where the pipeline code is tested 
first. pushes or released versions only go to productive Jenkins if well 
tested
- we "mocked" the pipeline DSL methods which enables us to at least do some 
basic groovy syntax and compilation tests. So far, Mockito, JUnit, Spock 
helps us a little.
- we developed some simple "integration-test" pipelines where we can test 
the pipeline code first - before testing or using it with real-life 
projects.

It´s currently a time-consuming and sometimes frustrating process to get 
things running - but we are looking forward to a lot of improvements coming 
soon.

Good luck, 

Torsten

-- 
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/df090766-3ba2-4e19-af8f-a57b5f97256c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trouble using shared pipeline libraries

[Torsten Reinhard]

can you provide some more info, especially
* how does your Jenkisfile look like
* do you have global shared library configured or per folder? 
* which version of the shared library do you adress? Is your script 
available in that version?
* do you have same script in the internal repo? 

Regards, Torsten

-- 
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/8a99c4a8-a20f-4a8d-8534-70c9fa82f51a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.