"Push Notification" for Jenkins

2020-03-30 Thread Andreas Tscharner
Hello World, We are in the process of updating Jenkins from version 2.150.3 to version 2.222.x. Our version control system is a git server which is in-house. Currently our "push notification" is an empty schedule for a "PollSCM" Build Trigger combined with a curl -s http://buildserver:8080/git/not

Re: Access to Gitlab Api Token via Credential Provider in a Job DSL Groovy Script

2020-03-30 Thread 'Sandra Parsick' via Jenkins Users
My colleague pointed me in. The trick is to iterate over all CredentialsProvider and filter by id: @Field def privateToken = CredentialsProvider .lookupCredentials(StandardCredentials, (Item) null, ACL.SYSTEM) .find { it.id == "gitlab-api" } .apiToken Am Freitag, 15. Mä

Re: Metrics & Figures about Jenkins Core and Jenkins Plug-ins

2020-03-30 Thread Manuel Jesús Recena Soto
Hello Oleg, On Mon, Mar 30, 2020 at 12:52 PM Oleg Nenashev wrote: > I think it would be a great addition to https://stats.jenkins.io/ > I don't know where this side-project will arrive, but it can be a great addition. > Would be great to see the code/backend behind this visualization > As I

Re: Metrics & Figures about Jenkins Core and Jenkins Plug-ins

2020-03-30 Thread Manuel Jesús Recena Soto
Typo: Releases: http://142.93.140.202/releases On Mon, Mar 30, 2020 at 9:56 PM Manuel Jesús Recena Soto wrote: > Hello Mark, > > If the selected year is the current year (aka 2020) everything rendered in > the UI is from *the last 356 days*. > > When you selected a specific year, for example, 2

Re: Metrics & Figures about Jenkins Core and Jenkins Plug-ins

2020-03-30 Thread Manuel Jesús Recena Soto
Hello Mark, If the selected year is the current year (aka 2020) everything rendered in the UI is from *the last 356 days*. When you selected a specific year, for example, 2019, what you see the what it happened over 2019. I have to prepare a basic documentation where I am able to explain some as

Re: Jenkins Upgrade

2020-03-30 Thread M.Madhusudana Reddy
Thanks Devin/Mark. I will try disabling jqs-monitoring first to see if the issue goes away. yes, we are using Tomcat and I will try with Jetty too. Thanks M.Madhu On Mon, Mar 30, 2020 at 2:23 PM Devin Nusbaum wrote: > From a quick look at the thread dumps, I think that the main problem is >

Re: Jenkins Upgrade

2020-03-30 Thread Devin Nusbaum
>From a quick look at the thread dumps, I think that the main problem is that >JQSMonitoring (from Job/Queue/Slaves Monitoring Plugin) ends up loading builds >in its constructor, which is invoked during Jenkins startup because it is a >RootAction >

Re: Jenkins Upgrade

2020-03-30 Thread Mark Waite
I'm afraid that it is much more difficult for anyone to assist with a problem that can't be duplicated. On Mon, Mar 30, 2020 at 12:42 PM M.Madhusudana Reddy wrote: > Thanks Mark. I can definitely try that. > > But again as I mentioned early, If I kill the process and start the > jenkins JVM(with

Re: Jenkins Upgrade

2020-03-30 Thread M.Madhusudana Reddy
Thanks Mark. I can definitely try that. But again as I mentioned early, If I kill the process and start the jenkins JVM(with the same JAVA version), I may not see this issue. This is intermittent and I need to keep trying with the restarts to reproduce the issue. Thanks M.Madhu On Mon, Mar 30,

Re: Jenkins Upgrade

2020-03-30 Thread Mark Waite
Any chance you can duplicate the same problem on Java 8 update 242 (the current release)? Java 8 u121 was released in Jan 2017. Significant changes were made to Java 8 in update 161 (WIkipedia says " 21 Security fixes, 3 new features, 9 changes and 1 bug fix from 8u152."). Update 231 (Oct 2019)

Re: Jenkins Upgrade

2020-03-30 Thread M.Madhusudana Reddy
I dumped the thread dump into one of the thread dump analysis tool and the tool is reporting on Dead Lock. Thread CpsStepContext.isReady [#4] is in deadlock with thread Finalizing set up Thanks M.Madhu On Mon, Mar 30, 2020 at 12:45 PM M.Madhusudana Reddy wrote: > Ok. I am able to reproduce th

Re: CI with Git in Jenkins

2020-03-30 Thread Mark Waite
On Mon, Mar 30, 2020 at 10:03 AM Roland Asmann wrote: > Thanks for the explanation. I do agree, I just thought it a bit weird > that there was a difference in behavior... > > I still would like to know, what the consensus is to writing the > Jenkinsfile: add polling or not? > Consensus is to not

Re: Pipeline Authentication Error

2020-03-30 Thread Sat
below worked for me, i never tried ssh: git@repourl/reponame.git On Monday, March 30, 2020 at 5:34:17 PM UTC+1, Alex M wrote: > > Hello, I’m trying to set up a Jenkins Pipeline that pulls from a git > repository on a remote server. I’m getting an authentication error when > using “Pipeline s

Pipeline Authentication Error

2020-03-30 Thread Alex M
Hello, I’m trying to set up a Jenkins Pipeline that pulls from a git repository on a remote server. I’m getting an authentication error when using “Pipeline script from SCM” but the same credentials work in my freestyle project using sshagent() and git clone. It also succeeds when verifying t

Re: CI with Git in Jenkins

2020-03-30 Thread Roland Asmann
Thanks for the explanation. I do agree, I just thought it a bit weird that there was a difference in behavior... I still would like to know, what the consensus is to writing the Jenkinsfile: add polling or not? Thanks. On 25.03.2020 14:53, Mark Waite wrote: Multibranch pipelines assume that

Re: Timeout in pipeline not aborting the build

2020-03-30 Thread Georg Lutz
Hi all, sorry, there went something wrong with formatting in my first email. :-/ Here is the hopefully correctly formatted version: I can't get the timeout option working correctly in pipeline scripts. What I expect is that if a define a timeout on the toplevel in the Jenkinsfile and a step

Re: Metrics & Figures about Jenkins Core and Jenkins Plug-ins

2020-03-30 Thread Oleg Nenashev
I think it would be a great addition to https://stats.jenkins.io/ Would be great to see the code/backend behind this visualization On Sunday, March 29, 2020 at 10:31:25 PM UTC+2, Mark Waite wrote: > > I'm not clear how you're calculating release counts in the table. I > initially assumed it was