slack-plugin

Hi, I am new for the open source contribution. I like to try to fix this bugs in slack-plugin. I choose a bug which is "Feature Request - Display both author and committer #219". But I don't understand from where to start. Therefore I need your help. Prabhashani. -- You received this message

Re: Job parameters in Jenkins 2.X

Thanks Daniel, I'll give that a go. On Thursday, 4 August 2016 10:00:31 UTC+10, Daniel Beck wrote: > > > > On 04.08.2016, at 01:56, Nick Grealy > wrote: > > > > As the plugin maintainer, can I inject variables programmatically, as > environment variables instead? > >

Re: Job parameters in Jenkins 2.X

> On 04.08.2016, at 01:56, Nick Grealy wrote: > > As the plugin maintainer, can I inject variables programmatically, as > environment variables instead? > EnvironmentContributor is the extension point for that. To pass parameters to the build, you could define a

Re: Job parameters in Jenkins 2.X

Thanks Baptiste, that's good to know (or not :( ). A bit of background, this is in regard to maintaining the poll-mailbox-trigger-plugin - I'll add it to the following list of "Plugins affected by fix

Jenkins Developers for a fun project

We are looking for experienced Jenkins developers to run a project for us in their sphere time. We are willing to pay $20 per hour and a minimum of $500 per the project. Please take a look at the project specs and let me know if you can perform this project at the required level. Have a great

Re: Most reliable way to get the build number of the build just executed using JS/jQuery

Markus, Thanks for the reply! Regarding the *add a parameter to the job that contains a UUID* comment, I'm trying to code this in such a way that it can easily be implemented on other Jenkins instances, so requiring a parameter to be added to any job that wants to use this would probably be a

Re: Job parameters in Jenkins 2.X

It won't work as of SECURITY-170. See https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11 for details. Can't you list all of those parameters with some left undefined depending on the build? Cheers Le 3 août 2016 8:54 PM, "Nick Grealy" a

Re: Job parameters in Jenkins 2.X

Ok, what happens when the parameter names are dynamic (ie. Not known in advance)? Should I be using environment variables instead? (How do I add them programmatically?) Thanks -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To

Re: Job parameters in Jenkins 2.X

You need to add "bbb" as a parameter to the job. Jenkins will now only pass thru parameters that are defined in the job that you are passing them to. On Wed, Aug 3, 2016 at 9:35 AM Nick Grealy wrote: > Hi all, > > This should be a simple question to answer... > > Before

Job parameters in Jenkins 2.X

Hi all, This should be a simple question to answer... Before Jenkins 2.X, I used to be able to execute a Job programatically with the following code: import jenkins.model.*; import hudson.model.*; // kick off a job... FreeStyleProject job = Jenkins.getInstance().getJob('QuickTest');

Immediate Interview: Java/Mobile Developer with Kony Exp is must

*Hello,Please let me know if you have any consultant available for the below role,* Role title: Mobile/java Developer with Kony Start Date: immediate End date: Long term Location: Atlanta, GA **Multiple Openings***Kony exp is must Job Description: The Web UX person will help

Re: Automate recommended plugin unittest run against latest Jenkins core

I don't understand why you would make that a GA criteria for releases, or for LTS releases. Can you explain in more detail what you're trying to confirm with that check? I had maintained a separate branch of the git client plugin which depended on the latest LTS release (called

Automate recommended plugin unittest run against latest Jenkins core

Hi, I created an issue[1] to verify if all recommended plugins has passing unittest when run against latest core. I would like to use that as a GA criteria for releases, LTS ones at least. I see people are still updating plugin-compat-tester so I guess it is not dead, though I did not

Re: WorkflowMultiBranchProject getLastBuild

With some experimenting I think I have gotten what I need. def jenkinsInstance = jenkins.model.Jenkins.getInstance() def jenkinsProject = "multiBranchPipelineProjectA/master" def project = jenkinsInstance.getItemByFullName(jenkinsProject) def job = project.getAllJobs().first() def lastBuild =

WorkflowMultiBranchProject getLastBuild

Have Jenkins projects as Multibranch pipeline: org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject extends jenkins.branch.MultiBranchProject extends com.cloudbees.hudson.plugins.folder.computed.ComputedFolder extends com.cloudbees.hudson.plugins.folder.AbstractFolder

Jenkins build issue

Hi team, I have the issue with org.jenkins-ci.tools:maven-hpi-plugin as in Plugin org.jenkins-ci.tools:maven-hpi-plugin

how to create 2 page in RootAction

Hi, I need to create the below option in UI when I implement the RootAction. User pres on the main menu ( left jenkins menu ) and get the first page with some drop downs fields. After he choose the value he need to press "Next" button and get the second page with additional data. How in jelly