Re: Not able to release new version of plugin

Thanks. In the effective POM, i have following: java.net-m2-repository http://maven.jenkins-ci.org/content/repositories/releases/ maven.jenkins-ci.org http://maven.jenkins-ci.org:8081/content/repositories/snapshots github-pages

Re: distributed build behavior, java.io.* classes, and security

Thanks for your reply. I discovered by trial and error today what you said about using FilePath. I changed all my java.io usage to FilePath and used a MasterToSlaveFileCallable subclass to accomplish my goal. What was not intuitive to me was that my Builder code is executed on master, while the

Re: Retrieving a list of Pipeline jobs

Thanks for the suggestions! Also, the historical background makes this much clearer. Neither of those classes have getTrigger() implemented, any tips for how to get build triggers from Job.class or WorkflowJob.class? On Thu, Jan 5, 2017 at 2:19 PM, Jesse Glick wrote: >

Re: Retrieving a list of Pipeline jobs

On Thu, Jan 5, 2017 at 3:45 PM, Emory Penney wrote: > I've noticed that > > Jenkins.getInstance().jenkinsInstance.getAllItems(AbstractProject.class); > > doesn't seem to get me a list of Pipelines jobs. I'm sure I need to use a > different class but I'm unclear which one.

Re: distributed build behavior, java.io.* classes, and security

On Tue, Dec 27, 2016 at 12:54 PM, Robert St. John wrote: > I am using the Credentials > plugin to load a keystore from a StandardCertificateCredential, which as I > understand ultimately uses FilePath to load the keystore from the master > node. Yes, existing Jenkins code

Re: Plugin that uses Acceptance Test Harness tests

On Thu, Dec 22, 2016 at 5:44 PM, Ullrich Hafner wrote: > I also do such plug-in integration tests before a release of my > plugins, but I run them from the ATH. There is a standing conflict between keeping all tests in one place, vs. all in plugin repositories. Both

Re: How can a plugin save output when running in pipeline

On Mon, Dec 26, 2016 at 4:13 PM, Christian McHugh wrote: > I'm a bit stuck on the conversion of SimpleBuildStep to full step needed to > have the pipeline syntax be able to return output to be saved into a > variable. > As I'm not a jenkins framework expert by any

RE: Can't create a compatibility alias for a credentials BaseStandardCredentials subclass and a Messages class

Hi, I think I figured it out. The credential plugin it’s using any of the XStream instances from Jenkins and it’s using the DEFAULT_XSTREAM member from XmlFile. Shouldn’t getConfigFile create a new XmlFile by providing the XSTREAM2 alias from Jenkins?

Retrieving a list of Pipeline jobs

Hi, Sorry for the noob question, I'm sure this is answered somewhere in the documentation I'm just completely unable to find it... I've noticed that Jenkins.getInstance().jenkinsInstance.getAllItems(AbstractProject.class); doesn't seem to get me a list of Pipelines jobs. I'm sure I need to

Re: [Experiment] Reviewers Team

On 2017-01-05 17:01, Daniel Beck wrote: On 10.08.2016, at 08:42, James Dumay wrote: All of the blueocean-plugin PRs mention the reviewers team... so If you are looking to get involved in Blue Ocean reviewing is a great place to start! FTR I asked that this practice

GSOC 17

Hello, I am looking forward to participate in GSOC'17 & am new to open source developmemt. Please can anyone help getting started ? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails

Can't create a compatibility alias for a credentials BaseStandardCredentials subclass and a Messages class

Hi, I have to change the package names and I'm trying to migrate the data from the old class. To accomplish this I've tried adding a compatibility alias during initialization and it works for other classes I had to rename, but not for the credentials class and Messages (the auto-generated class

Re: [Experiment] Reviewers Team

> On 10.08.2016, at 08:42, James Dumay wrote: > > All of the blueocean-plugin PRs mention the reviewers team... so If you are > looking to get involved in Blue Ocean reviewing is a great place to start! FTR I asked that this practice be stopped a few weeks ago, as it

Re: [Experiment] Reviewers Team

> On 05.01.2017, at 16:44, Jacob Larfors wrote: > > just checking that the @jenkinsci/code-reviewers group is still around It's still around and configured to be visible. However, you're not a member of the jenkinsci GitHub organization as you haven't accepted the

Re: [Experiment] Reviewers Team

Hello, just checking that the @jenkinsci/code-reviewers group is still around? Doesnt seem to exist in GitHub anymore... at least I get a 404 error not found https://github.com/orgs/jenkinsci/teams/code-reviewers I was hoping to get

Re: Not able to release new version of plugin

> On 05.01.2017, at 15:15, Irfan Sayed wrote: > > still the same error Unsurprising given that this still referenced the host name that has been shut down. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To

Re: Not able to release new version of plugin

Thanks Daniel. i added following in plugin POM: java.net-m2-repository http://maven.jenkins-ci.org/content/repositories/releases/ still the same error. i am not getting from where it is picking up that url and port number. in my settings.xml as well this URL is not

Re: Not able to release new version of plugin

> On 05.01.2017, at 15:02, Irfan Sayed wrote: > > In my plugins POM, i have already this: What about distributionManagement? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop

Re: Not able to release new version of plugin

Thanks Daniel. In my plugins POM, i have already this: repo.jenkins-ci.org http://repo.jenkins-ci.org/public/ repo.jenkins-ci.org http://repo.jenkins-ci.org/public/ is this not correct ? Regards, On Thu, Jan 5, 2017 at 5:57 AM, Daniel Beck

Re: Not able to release new version of plugin

> On 05.01.2017, at 14:49, Irfan Sayed wrote: > > it seems that URL : > http://maven.jenkins-ci.org:8081/content/repositories/releases is not working. > Can someone please suggest ? Second item at