Re: [Jenkins-infra] JIRA downtime/maintenance window scheduled for 2017-03-04 16:00 UTC

[R. Tyler Croy]

(replies inline)

On Mon, 27 Feb 2017, R. Tyler Croy wrote:

> 
> I'm planning on performing a scheduled upgrade of JIRA (issues.jenkins-ci.org)
> this Saturday at 16:00 UTC / 8:00 PST. I don't expect the work to last longer
> than 60 minutes, but please expect JIRA to be offline for at least the full
> hour.
> 
> The JIRA tracking this (hehe) is:
> 


JIRA has been upgraded, yay.



- R. Tyler Croy

--
 Code: 
  Chatter: 
 xmpp: rty...@jabber.org

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--

-- 
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/20170304162314.o6iyyphwiihqwzgp%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

jenkins API credential issues

[Richard Zilahi]

Hi Guys! 

I am having some issue with credentials when using jenkins. 

I have created a token for the job, and then a token a token for the user i am 
building the JOB with, and using the following sytanx for the job to be 
executed from a script: 

http://:@/jenkins/job//buildWithParameters?token=&gitrepo="+gitrepoPath+"&testcase="+tctorun

This approach working as long as I am logged in jenkins whichever user, so not 
necessarily with the robot user, but for example admin user, the script 
execution works. 

If i am not logged in jenkins, the script return “Forbidden” error, which i 
assume have something to do with the credentials, but as I have provided the 
tokens, I can’t really figure out what caueses the issue. 

It would be nice if someone could give me a hand in solving this issue, becasue 
it would have been a huge security issue to open jenkins for everyone, using 
the “Everyone can do anything” option. 

Do you have any ideas what I am missing here? 

Thank you in advance, 

Richard Z.

-- 
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/F753A717-23E2-43E6-A4EB-C6FFB76D5EF7%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Pipeline locks occasionally allowing concurrent execution?

[Jonathan del Strother]

Hi there - Has anyone run into problems with pipeline's lock command?  On a
multibranch project with 2 nodes (master + 1 slave), it occasionally seems
to allow two concurrent jobs to acquire the same lock.   I have Jenkins
2.45 with Lockable Resources 1.11 and Pipeline 2.9.

-- 
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/b55f7aa3-3a23-4e65-850d-389aed98a792%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.