Re: Removing name autocompletion in new job creation

The autocomplete parameter is not specified in jelly so I believe it is browser behavior remembering name="name" input. In #2501 pull request I propose to move input box so that autocomplete will not hide warning message. What do you think?

[Plugin] Poll Jobs Hosted on various Jenkins Servers

Hi There, I have a simple requirement to link 2 different Jenkins instance but unable to find any plugin that I can use directly to poll changes from another Jenkins instance with read-only access. Dev team is managing another Jenkins instance and they have given read-only access to all so if

Re: Interested in building your plugin on ci.jenkins.io?

Hi Tyler, Can you point me to some docs on setting that up. I would like to create that setup for the tfs jenkins plugin. Manfred On Mon, Aug 8, 2016 at 8:48 AM, R. Tyler Croy wrote: > Howdy there, your friendly project infrastructure dude here. I'm hoping to > get > more

Re: Whither javadoc?

(replies inline) On Mon, 08 Aug 2016, Greg Allen wrote: > Must be. Sorry for the spam. I found that our secondary nameserver wasn't properly serving the new A record for javadoc.jenkins.io. Depending on whichever your nameserver would go to for caching records, it might get an NXDOMAIN. That

Re: Whither javadoc?

Must be. Sorry for the spam. On 08/08/2016 05:31 PM, Richard Bywater wrote: That link is working for me - wonder if your DNS is playing up? Richard. On Tue, 9 Aug 2016 at 09:22 Greg Allen > wrote: Has the javadoc moved somewhere? Trying

Re: Whither javadoc?

That link is working for me - wonder if your DNS is playing up? Richard. On Tue, 9 Aug 2016 at 09:22 Greg Allen wrote: > Has the javadoc moved somewhere? Trying http://javadoc.jenkins.io/ is > not working for any of the releases I have tried. I am getting >

Whither javadoc?

Has the javadoc moved somewhere? Trying http://javadoc.jenkins.io/ is not working for any of the releases I have tried. I am getting ERR_NAME_NOT_RESOLVED. But other links off of https://jenkins.io/doc/ seem to be fine. Thanks, -- Greg -- You received this message because you are

Re: Interested in building your plugin on ci.jenkins.io?

On Mon, Aug 8, 2016 at 2:17 PM, Mark Waite wrote: > I hope one day to be able to use the Jenkinsfile to run and report findbugs > warnings, to run and report code coverage, and more. I would expect all that to be part of the standard script; there is nothing

Re: Interested in building your plugin on ci.jenkins.io?

On Mon, Aug 8, 2016 at 1:21 PM R. Tyler Croy wrote: > (replies inline) > > On Mon, 08 Aug 2016, Mark Waite wrote: > > > Is there an eventual evolution planned to move to using the GitHub > > Organizations Folder plugin to build and test pull requests for subsets > of > > the

Re: Interested in building your plugin on ci.jenkins.io?

(replies inline) On Mon, 08 Aug 2016, Mark Waite wrote: > Is there an eventual evolution planned to move to using the GitHub > Organizations Folder plugin to build and test pull requests for subsets of > the jenkinsci GitHub organization? > > I was quite impressed with the results of my quick

Re: Interested in building your plugin on ci.jenkins.io?

(replies inline) On Mon, 08 Aug 2016, Jesse Glick wrote: > On Mon, Aug 8, 2016 at 11:48 AM, R. Tyler Croy wrote: > > If your plugin > > repository already has a `Jenkinsfile`, or you're interested in creating one > > for your plugin, I would love to have your plugin built

Re: [icescrum-plugin] Can't release an update 401, no work around worked :'(

Artifactory login is back :-) And.. I was able to release! Thank you! On Mon, Aug 8, 2016 at 8:37 PM, Vincent Barrier wrote: > Yes I still getting: "Username or Password Are Incorrect" and I may abuse > of forgot password link, JSON answer:"error": "The

Re: [icescrum-plugin] Can't release an update 401, no work around worked :'(

Yes I still getting: "Username or Password Are Incorrect" and I may abuse of forgot password link, JSON answer:"error": "The specified user is not permitted to reset his password." On Mon, Aug 8, 2016 at 8:32 PM, Baptiste Mathus wrote: > Oops. Probably not yet actually >

Re: [icescrum-plugin] Can't release an update 401, no work around worked :'(

Oops. Probably not yet actually Follow http://lists.jenkins-ci.org/pipermail/jenkins-infra/2016-August/000818.html for last updates. Le 8 août 2016 8:29 PM, "Baptiste Mathus" a écrit : > Hi Vincent, > > Did you check you can login through the accounts UI? There was a >

Re: [icescrum-plugin] Can't release an update 401, no work around worked :'(

Salut Baptiste :) Le lundi 8 août 2016, Baptiste Mathus a écrit : > Hi Vincent, > > Did you check you can login through the accounts UI? There was a > vulnerability some months ago which led to resetting passwords, did you > release recently/since that? > Yes it works > Or

Re: [icescrum-plugin] Can't release an update 401, no work around worked :'(

Hi Vincent, Did you check you can login through the accounts UI? There was a vulnerability some months ago which led to resetting passwords, did you release recently/since that? Or likely, the infra issue reported by the jfrog guys was the /culprit/. Note that they reported that they changed

Re: [icescrum-plugin] Can't release an update 401, no work around worked :'(

Ok I will retry when I will be able to login my username / password from jenkins.io Thanks Le lundi 8 août 2016, Daniel Beck a écrit : > We are currently experiencing problems Artifactory, likely due to > yesterday's maintenance. It's currently not possible to log in with any

Re: [icescrum-plugin] Can't release an update 401, no work around worked :'(

Le lundi 8 août 2016, Slide a écrit : > You have your settings.xml setup with your Jenkins username/password? (NOT > github username/password) > Yes (and it's the same as github) > > On Mon, Aug 8, 2016 at 10:04 AM Vincent Barrier

Re: Interested in building your plugin on ci.jenkins.io?

On Mon, Aug 8, 2016 at 12:06 PM Jesse Glick wrote: > On Mon, Aug 8, 2016 at 11:48 AM, R. Tyler Croy > wrote: > > If your plugin > > repository already has a `Jenkinsfile`, or you're interested in creating > one > > for your plugin, I would love to have

Re: Interested in building your plugin on ci.jenkins.io?

On Mon, Aug 8, 2016 at 11:48 AM, R. Tyler Croy wrote: > If your plugin > repository already has a `Jenkinsfile`, or you're interested in creating one > for your plugin, I would love to have your plugin built on our existing > Jenkins-on-Jenkins. I continue to advocate having

Re: WorkflowMultiBranchProject getLastBuild

On Mon, Aug 8, 2016 at 4:31 AM, Sverre Moe wrote: > I just need the last build from an upstream dependency. The upstream build > cause might be an upstream dependency, or it may be an SCM cause. Such that > the upstream project might not be the upstream cause. Also an

Re: [icescrum-plugin] Can't release an update 401, no work around worked :'(

We are currently experiencing problems Artifactory, likely due to yesterday's maintenance. It's currently not possible to log in with any account I think. > On 08.08.2016, at 19:19, Slide wrote: > > You have your settings.xml setup with your Jenkins username/password?

Re: [icescrum-plugin] Can't release an update 401, no work around worked :'(

You have your settings.xml setup with your Jenkins username/password? (NOT github username/password) On Mon, Aug 8, 2016 at 10:04 AM Vincent Barrier wrote: > As Daniel Beck suggested, I changed to a newer parent POM version: 2.12 ( >

Re: [icescrum-plugin] Can't release an update 401, no work around worked :'(

As Daniel Beck suggested, I changed to a newer parent POM version: 2.12 ( https://github.com/jenkinsci/icescrum-plugin/commit/75bbdcd2b7ffbac242daaf847ee6f569ef59f0bc ) Still no luck :( Any other advices? On Mon, Aug 8, 2016 at 5:18 PM, Vincent Barrier wrote: > Hi

Re: Backporting for LTS 2.7.3 started

https://github.com/jenkinsci/jenkins/pull/2500 is something that we really need and it should be very low risk On 8 August 2016 at 13:00, Oliver Gondža wrote: > Backporting has started and the RC is scheduled for 2016-08-17. I consider > leaving JENKINS-35493 out unless

Re: Interested in building your plugin on ci.jenkins.io?

I see the git plugin but not the git client plugin. What's the link? On Mon, Aug 8, 2016, 10:09 AM R. Tyler Croy wrote: > (replies inline) > > On Mon, 08 Aug 2016, Mark Waite wrote: > > > I'd like the git client plugin built on https://ci.jenkins.io/ if > > possible. It

Re: Interested in building your plugin on ci.jenkins.io?

Is there an eventual evolution planned to move to using the GitHub Organizations Folder plugin to build and test pull requests for subsets of the jenkinsci GitHub organization? I was quite impressed with the results of my quick experiments with the GitHub Organizations Folder plugin. Mark Waite

Re: Interested in building your plugin on ci.jenkins.io?

(replies inline) On Mon, 08 Aug 2016, Mark Waite wrote: > I'd like the git client plugin built on https://ci.jenkins.io/ if > possible. It already has a Jenkinsfile on its active branches, and has > been running tests in my various development and test environments from > that Jenkinsfile.

Programmatically reuse Credentials from the SCM plugin

I'm developing a plugin that depends on the Team Concert plugin . *TC plugin* has a Credentials field, used to connect to the Team Concert server. My plugin -- as a Build Step -- should reconnect to the server using the same

Re: Interested in building your plugin on ci.jenkins.io?

I'd like the git client plugin built on https://ci.jenkins.io/ if possible. It already has a Jenkinsfile on its active branches, and has been running tests in my various development and test environments from that Jenkinsfile. Mark Waite On Mon, Aug 8, 2016 at 9:48 AM R. Tyler Croy

Interested in building your plugin on ci.jenkins.io?

Howdy there, your friendly project infrastructure dude here. I'm hoping to get more accurate usage requirements for our eventual migration of https://ci.jenkins.io, and the rest of our infra, to Azure [0]. If your plugin repository already has a `Jenkinsfile`, or you're interested in creating one

[icescrum-plugin] Can't release an update 401, no work around worked :'(

Hi guys, I'm the maintainer of icescrum-plugin, I need to deploy a new version of this plugin but each time I do a man release:perform, I get an error : [INFO] BugInstance size is 0 > [INFO] Error size is 0 > [INFO] No errors/warnings found > [INFO] > [INFO] ---

Re: Removing name autocompletion in new job creation

Is autocomplete of the job name an actual feature, or just something that's there by default from the browser? If autocomplete must stay, maybe the placement of the validation warnings could be moved e.g. above the input? On Monday, August 8, 2016 at 1:06:19 PM UTC+1, Samat Davletshin wrote: >

Removing name autocompletion in new job creation

Hello! In my Pull Request I propose to make name validation of a new job more interactive. https://github.com/jenkinsci/jenkins/pull/2416 However, it was noted that because of autocomplete the warning message will not always be visible. Do you think that I should remove the autocomplete of

Backporting for LTS 2.7.3 started

Backporting has started and the RC is scheduled for 2016-08-17. I consider leaving JENKINS-35493 out unless someone feels strongly. Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 Fixed: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.7.3-fixed Fixed:

Re: WorkflowMultiBranchProject getLastBuild

It is related somewhat. That issue is about getting the upstream build that triggered this running build. I just need the last build from an upstream dependency. The upstream build cause might be an upstream dependency, or it may be an SCM cause. Such that the upstream project might not be the

RE: Vulnerability analysis question

Thanks I think this should cover it. -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Daniel Beck Sent: 05 August 2016 22:51 To: jenkinsci-dev@googlegroups.com Subject: Re: Vulnerability analysis question Jenkins does not