nterested in merging/enhancing other job types.
> There is a workaround by using any-build-step/flexible publisher plugins
> that expose types vice versa.
>
> On Monday, December 12, 2016 at 7:18:36 PM UTC+3, Dan Alvizu wrote:
>>
>> Hi,
>>
>> I'm working on th
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
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
-dev/CABffhO6wu79KwWgHe%3Db3QrjDs1ZmbWzLLuWTSgxdXh5Y4wOfAQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
[image: Ping Identity logo] <https://www.pingidentity.com/>
Dan Alvizu
Principal Engineer
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
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:
>
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 chan
+Secure+Passwords
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
> config or password since then and I am now getting a 401 error attempting
> to upload:
>
> ```
&
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
https://github.com/dalvizu/jira-ext-plugin
Plugin Name: jira-ext-plugin
My GitHub username: dalvizu
Existing repo: https://github.com/dalvizu/jira-ext-plugin
Doc: https://github.com/dalvizu/jira-ext-plugin
The jira-ext plugin attempts to integrate to Atlassian JIRA in an
extensible way.
display/JENKINS/Hosting+Plugins for
> details.
>
> Cheers
>
> 2016-01-04 22:37 GMT+01:00 Dan Alvizu <alv...@gmail.com >:
>
>> https://github.com/dalvizu/jira-ext-plugin
>>
>> Plugin Name: jira-ext-plugin
>> My GitHub username: dalvizu
>> Ex
Ah, got it! Thanks Daniel!
On Tuesday, November 10, 2015 at 2:34:23 PM UTC-7, Daniel Beck wrote:
>
> Accept the invitation in your spam folder, or on github.com/jenkinsci.
>
> On 10.11.2015, at 17:41, Dan Alvizu <dal...@pingidentity.com >
> wrote:
>
> >
n solved issues and review other (older) PR.
>
> Regards,
>
> 2015-11-09 17:17 GMT+01:00 Dan Alvizu <dalv...@pingidentity.com>:
> > Hi,
> >
> > Sorry for the bump again. I think that Manuel replying to this makes it
> seem
> > that this is responded to
I guess I am confused, and maybe we both are as this has been a few weeks
old, and there is a language barrier: I had written to you privately asking
to be a maintainer and to help out, and you told me to ask here, as it was
the place for such requests.
If you do not want me to be a
ine-plugin/pull/79#issuecomment-146625699
>
>
> Regards,
>
> 2015-10-20 17:12 GMT+02:00 Dan Alvizu <alv...@gmail.com >:
> > Hello,
> >
> > I'd like to have commit access to the build-pipeline-plugin
> > (https://github.com/jenkinsci/build-pipeline-p
Hi,
I am using the Job DSL plugin on my project. I have a proprietary plugin,
part of which is
a provider of parameters for the parameterized-trigger plugin. This allows
me to trigger
a deployment with properties specified by my plugin:
```
* public class *MyCustomBuildParameters
Hello,
I'd like to have commit access to the build-pipeline-plugin
(https://github.com/jenkinsci/build-pipeline-plugin). I believe the
original authors (centrum systems) no longer maintain it, and only recena
is involved. I e-mailed him directly and he 302'd me here. I'd like to help
out with
I'm interested in being a maintainer, if you need help. I have a few
pending PRs myself:
https://github.com/jenkinsci/build-pipeline-plugin/pull/89
https://github.com/jenkinsci/build-pipeline-plugin/pull/79
On Wednesday, October 7, 2015 at 2:24:34 PM UTC-6, Manuel Recena Soto wrote:
>
>
Hi,
I just wrote this wiki page on how to do dependency injection in a plugin:
https://wiki.jenkins-ci.org/display/JENKINS/Dependency+Injection
I want to use this so that I can provide a move requests to external
resource to a service class and pass a mock to my Publisher during unit
tests.
19 matches
Mail list logo
