Can't get "negative readahead" to work

We have two types of builds on our Jenkins server, CI incremental builds and then (one for each CI job) a nightly build that does a full clean build for QA. I want to create two views to show these separately. The nightly view is easy as all the jobs are called xxx_Nightly, however I can't get

Re: Can't get "negative readahead" to work

On 22.07.2014, at 09:00, Mark Syms wrote: > The help indicates that (?!_Nightly) should be the magic regex that is needed > but I either end up with nothing selected or every build selected. > > Does this negative readahed regex actually work for filtering jobs or am I > just doing it wrong?

Re: Can't execute Maven 2 on the slave where Maven 3 is installed

There is also a configuration on jenkins under the slave for tool versions. On 21 Jul 2014 11:49 PM, "vicki_kozel via Jenkins Users" < jenkinsci-users@googlegroups.com> wrote: > Hello, > most of our projects are built with Maven 3. We have a request though to > build one project with Maven 2. > I

Re: Can't get "negative readahead" to work

That did it, thanks Daniel. On 22 July 2014 08:38, Daniel Beck wrote: > > On 22.07.2014, at 09:00, Mark Syms wrote: > > > The help indicates that (?!_Nightly) should be the magic regex that is > needed but I either end up with nothing selected or every build selected. > > > > Does this negativ

RE: Can't execute Maven 2 on the slave where Maven 3 is installed

We have both Maven2 and 3 installed and working across our Jenkins infrastructure. You should take a closer look at your master/slave configuration; you define the tools in the master, but also have to include the configuration in the slave; below is a part example of one of our Linux slaves.

What to do about NullPointerException (possibly associated with Naginator plugin)?

Hi I periodically see the following exception in the Jenkins log. I am running Jenkins 1.570. What can I do to find the reason for this please? Best regards David == Jul 22, 2014 10:06:55 AM WARNING hudson.ExpressionFac

Hot to run Jenkins BUILD only if GIT commit's COMMENT value "equals to..."

Hello everyone, I've setup an Android-Gradle job on Jenkins, that is triggered by a webhook on GitHub. Now, *I'd like to have the Jenkins run the build only for 'release' commits and not every update. *So decided to condition this by searching the commit's COMMENT for a specific value/string (

Regex in securitybased role strategy

Hi friends, I am struggling with regular expressions and they drive me atm to Nutsville! There is a set of jobs and they look like this: GUIDE_DISPATCHER GUIDE_CB_xxx_P4 MB_GUIDE_HEAD MB_GUIDE_PAG_P4 MB_GUIDE_MIB_D_BILBAO I am now trying to remove the view of everything that either has an MIB or

Re: Hot to run Jenkins BUILD only if GIT commit's COMMENT value "equals to..."

If you're willing to consider a slightly different approach, you could decide that you'll modify only certain files for release (like a version number file, or a file named "release"), and then use the git plugin's "Additional Behaviour" section to add "Polling ignores commits in certain paths", th

Re: Hot to run Jenkins BUILD only if GIT commit's COMMENT value "equals to..."

Hi Mark, thanks for the quick reply! I will see if this form of conditioning can fit our needs and reply here with the results.. If you or anyone come up with other solutions for this matter - please post it here :) Thanks! -Elad On Tuesday, July 22, 2014 3:45:44 PM UTC+3, Mark Waite wrote: >

Re: Jenkins App

Herman De Vries (2014-07-04 10:23): Hi all, We have developed a jenkins app to monitor all jobs, builds, artifacts and console outputs and on top to easy install the APKs of Android jobs. It would be great if you

Re: Hot to run Jenkins BUILD only if GIT commit's COMMENT value "equals to..."

Hello Bjorn, Should it be simpler for the intermediate job to check this? Can't I implement the same validation/check method in the main job? Thanks, Elad. On Tuesday, July 22, 2014 6:18:35 PM UTC+3, Björn Pedersen wrote: > > > Another idea would be not to trigger your job directly , but u

Re: Hot to run Jenkins BUILD only if GIT commit's COMMENT value "equals to..."

Another idea would be not to trigger your job directly , but use a small intermediate job that checks the log first and then triggers your job only if the message suits. Conditional Buildstep plugin or promoted buils come to mind here. Björn -- You received this message because you are subscr

Manual trigger failing in build pipeline with "No upstream trigger found for this project"

I've created a pipeline using the Build Pipeline plugin connecting 5 jobs like this: poll --> build-A --> deploy --> build-B --> deploy --> build-C --> deploy The poll job has a "Build other projects (manual step)" post-build action with "build-A, build-B, build-C" as the do

Re: Can't execute Maven 2 on the slave where Maven 3 is installed

Thank you for the responses! So, in the configuration for the slave - the name of the tool should match the name of the tool config on the Master? On Monday, July 21, 2014 2:49:40 PM UTC-7, vicki...@yahoo.com wrote: > > Hello, > most of our projects are built with Maven 3. We have a request thoug

Re: Regex in securitybased role strategy

Jan Seidel (2014-07-22 14:06): Hi friends, I am struggling with regular expressions and they drive me atm to Nutsville! There is a set of jobs and they look like this: GUIDE_DISPATCHER GUIDE_CB_xxx_P4 MB_GUIDE_HEAD MB_GUIDE_PAG_P4 MB_GUIDE_MIB_D_BILBAO I am now trying to remove the view of e

Re: Jenkins talking to another Jenkins instance

Has anyone seen an issue where when you go to add the post-build action in your job the option for "trigger a remote parameterized job" is not in the list even though the plugin is installed? On Monday, July 14, 2014 1:01:06 PM UTC-4, pcampbell wrote: > > That looks like it would do the job.

Re: What to do about NullPointerException (possibly associated with Naginator plugin)?

This issue seems to be fixed but the fix not yet released, so building a snapshot of naginator plugin and installing that should work. https://github.com/jenkinsci/naginator-plugin/commit/6789567dd81904efa775019c7b114144238612ec On 22.07.2014, at 12:52, David Aldrich wrote: > Hi > > I period

Issues with a job configured to build any git 'feature' branch.

Our workflow using git is similar to the GitFlow model that is now commonly used by many developer teams. In particular, we create feature branches that use the prefix feature/, and we have a Jenkins job configured to build any push to

Re: Issues with a job configured to build any git 'feature' branch.

I thought I remembered a pull request submitted to the git plugin to allow user definition of the comparison base. In your case, there is a "base branch" against which you want all comparisons, no matter the results of the last job. Unfortunately, I didn't find it in the current pull requests for

Re: Manual trigger failing in build pipeline with "No upstream trigger found for this project"

The solution: make sure there are only commas separating the projects to build specified in the post-build action. This pull request should fix the problem: https://github.com/jenkinsci/build-pipeline-plugin/pull/47 - David On Tuesday, July 22, 2014 6:30:35 PM UTC+3, David Resnick wrote: > > I'

Re: Issues with a job configured to build any git 'feature' branch.

Hi Mark, thanks for the reply. On Tuesday, July 22, 2014 12:39:52 PM UTC-7, Mark Waite wrote: > > I thought I remembered a pull request submitted to the git plugin to allow > user definition of the comparison base. In your case, there is a "base > branch" against which you want all comparisons,

Re: Issues with a job configured to build any git 'feature' branch.

On Tue, Jul 22, 2014 at 5:30 PM, Jim Lloyd wrote: > Hi Mark, thanks for the reply. > > On Tuesday, July 22, 2014 12:39:52 PM UTC-7, Mark Waite wrote: >> >> I thought I remembered a pull request submitted to the git plugin to >> allow user definition of the comparison base. In your case, there is

Re: Issues with a job configured to build any git 'feature' branch.

On Tue, Jul 22, 2014 at 5:37 PM, Mark Waite wrote: > On Tue, Jul 22, 2014 at 5:30 PM, Jim Lloyd wrote: > >> Can't you obtain the results you want (on your different, but related >>> concern) by asking your developers to push a new branch for changes which >>> are to be built independently, rathe

Can't anymore get a response when creating a job with curl

Hello, I used to be able to start a job with "buildWithParameters" using curl and to get a json response containing information such as the future build number (nextBuildNumber) and the queueItem. Without changing anything I am not receiving the response body any more. I didn't use this code f

Can't get a response body any more when launching a job via curl

Hello, I used to be able to start a job with "buildWithParameters" using curl and to get a json response containing information such as the future build number (nextBuildNumber) and the queueItem. Without changing anything I am not receiving the response body any more. I didn't use this code f