Re: Making a plugin with the same hudson.task.Builder and hudson.task.Publisher implementation

Okay, I was hoping there was some BuilderPublisher class I could just extend :) I'll go copy-pasta route. Thanks! On Monday, December 12, 2016 at 12:36:43 PM UTC-7, Kanstantsin Shautsou wrote: > > Unfortunately freestyle build is not freestyle. I guess because of > workflow nobody interested

Making a plugin with the same hudson.task.Builder and hudson.task.Publisher implementation

Hi, I'm working on the jira-ext plugin, which updates JIRA tickets as a hudson.task.Builder, which means it shows up in the drop-down of build steps. I would also like to have it show up in the list of post-build steps, which I understand means I must extend a hudson.task.Publisher. I can

Re: I can't use archetype and set java.version to "8"

I can confirm this fixes the issue. Thanks Jesse! On Wednesday, April 13, 2016 at 1:28:59 PM UTC-6, Jesse Glick wrote: > > I released version 2.7 of the POM with this fix. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe

Re: I can't use archetype and set java.version to "8"

Awesome thanks! On Tue, Apr 12, 2016 at 1:43 PM, Manfred Moser wrote: > Nice ;-) > > On Tue, Apr 12, 2016 at 12:39 PM, Jesse Glick > wrote: > >> On Fri, Apr 8, 2016 at 5:04 PM, Manfred Moser wrote: >> > Yes there is. We got this

I can't use archetype and set java.version to "8"

I followed the instructions in the plugin tutorial to create a new plugin, and I can't seem to use java 8 this way: https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial $ mvn -U org.jenkins-ci.tools:maven-hpi-plugin:create $ # open up pom.xml, change 'java.version' to 8 $ mvn package

Re: Unauthorized on upload to http://repo.jenkins-ci.org/

https://issues.jenkins-ci.org/browse/INFRA-588 Work-around in the comments On Sunday, March 6, 2016 at 9:16:05 PM UTC-7, Mark Waite wrote: > > When I attempted to release a new version of the git client plugin today, > the "mvn release:prepare release:perform" command failed with the message: >

Re: Can't maven release my plugin - 401 on upload to repo.jenkins-ci.org

Here's the JIRA ticket in case anyone else has the same issue (401 uploading to artifactory) https://issues.jenkins-ci.org/browse/INFRA-588 On Tuesday, March 1, 2016 at 1:51:10 PM UTC-7, Dan Alvizu wrote: > > Hi, > > I'm trying to do a third release of my plugin - I haven't changed my maven >

Re: Can't maven release my plugin - 401 on upload to repo.jenkins-ci.org

I'm able to upload my artifact to SNAPSHOT in the artifactory UI. I'm also storing my password in cleartext in my settings.xml -- is it possible an artifactory setting changed to require encrypted passwords? That config would be here:

Can't maven release my plugin - 401 on upload to repo.jenkins-ci.org

Hi, I'm trying to do a third release of my plugin - I haven't changed my maven config or password since then and I am now getting a 401 error attempting to upload: ``` [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project

Re: Commit access to build-pipeline-plugin

I'm looking to be a maintainer of the plugin, as I think I have enough knowledge to be helpful. On Mon, Nov 9, 2015 at 9:21 AM, Manuel Jesús Recena Soto wrote: > Looks like you are asking for access only for to get your PR merged. > > Be patient, I'm working on solved issues