[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Itai Sanders commented on JENKINS-33841 Re: Support for pipeline builds Yevhenii Kurtov: I need to see the pipeline code to be certain, but from the snippet you posted it seems like you activated the bitbucketnotifier before the checkout stage. Proceeding [Pipeline] bitbucketStatusNotify [Pipeline] stage (Checkout) the notifier is looking for the scm object instance, which in pipelines (unlike the freestyle jobs) is only initiated when you go through the scm checkout step, so basically you are calling for bitbucketnotifier with an uninitiated (null) scm object. it might be best if the plugin catches this and posts a more friendly exception message. maybe I'll look into it and post another pull request later if no one gets to it. let me know if placing the scm checkout before the bitbucketnotifier step worked or it's something else entirely. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37237) Emulator:Error getting device platform version
Title: Message Title satish kumar G V created an issue Jenkins / JENKINS-37237 Emulator:Error getting device platform version Issue Type: Bug Assignee: Christopher Orr Components: android-emulator-plugin Created: 2016/Aug/07 6:37 AM Environment: Windows10, Jenkins2.7.1, Android Emulator 2.15, Appium 1.5.3 Priority: Minor Reporter: satish kumar G V The emulator created successfully and appium services started. Appium detects the device also. $ F:\Android\sdk/tools/android.bat list target [android] Using Android SDK: F:\Android\sdk $ F:\Android\sdk/platform-tools/adb.exe start-server * daemon not running. starting it now on port 5818 * * daemon started successfully * $ F:\Android\sdk/platform-tools/adb.exe start-server [android] Starting Android emulator $ F:\Android\sdk/tools/emulator.exe -engine classic -ports 5754,5755 -report-console tcp:5866,max=60 -avd Android_5_0_API_21 -no-snapshot-load -no-snapshot-save emulator: WARNING: VM heap size set below hardware specified minimum of 192MB emulator: WARNING: Setting VM heap size to 384MB emulator: WARNING: Classic qemu does not support SMP. The hw.cpu.ncore option from your config file is ignored. emulator: device fd:1172 HAXM is working and emulator runs in fast virt mode [android] Emulator reported that the console is available on port 5,754 [android] Waiting for emulator to finish booting... $ F:\Android\sdk/platform-tools/adb.exe -s emulator-5754 wait-for-device shell getprop init.svc.bootanim Your emulator is out of date, please update by launching Android Studio: - Start Android Studio - Select menu "Tools > Android > SDK Manager"
[JIRA] (JENKINS-37236) Unable to negotiate
Title: Message Title Ronald Petty created an issue Jenkins / JENKINS-37236 Unable to negotiate Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Aug/07 2:56 AM Environment: Ubuntu 16.04.1, Jenkins 2.17, Java 8 Labels: SSH CORE Priority: Minor Reporter: Ronald Petty Hi, I am under the belief that the default setup (plugins) of Jenkins (2.17) listens for SSHD connections. It appears to default to an insecure key exchange algorithm. The by-pass is trivial, but unclear if its documented (in Jenkin's docs, I haven't found it.) Also, I haven't found anything mentioning the server side will be updated (another comment in docs might be good for that.) user@ubuntu:~$ ssh -p 34213 admin@localhost version Unable to negotiate with ::1 port 34213: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1 user@ubuntu:~$ ssh -oKexAlgorithms=+diffie-hellman-group1-sha1 -p 34213 admin@localhost version 2.17 I might be missing information, but haven't found anything on this yet (aside from people doing the aforementioned workaround.)
[JIRA] (JENKINS-37188) 2nd failure emails being sent even when build is successful with job-dsl-plugin
Title: Message Title David van Laatum closed an issue as Fixed 2.47 released which should fix Jenkins / JENKINS-37188 2nd failure emails being sent even when build is successful with job-dsl-plugin Change By: David van Laatum Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://grou
[JIRA] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Mark Waite edited a comment on JENKINS-20941 Re: Stored git credentials not used when submodule is updated My goal is to release it in time for Jenkins World (Sep 13-15, 2016), in combination with the switch of the git client plugin and git plugin to Java 7. That will require a minimum version of Jenkins 1.625, and requires some detailed review of other plugins since it also includes an update from JGit 3 to JGit 4. The update from JGit 3 to JGit 4 simplifies the git client plugin by allowing it to use Java 7 "try with resources". It (unfortunately) also requires that dependent plugins either upgrade to handle the change, or adapt to allow them to be used with either JGit 3 or JGit 4. The precise One coexistence technique is still being investigated now included in git plugin 2 . 5.3. Refer to [commit 71946a2|https://github.com/jenkinsci/git-plugin/commit/71946a2896d3adcd1171ac59b7c45bacaf7a9c56] for the details. The maintenance is already happening to regularly merge the git plugin master branch to the [3.0.0-beta branch|https://github.com/jenkinsci/git-plugin/commits/3.0.0-beta]. Likewise, the maintenance is already happening to regularly merge the git client plugin master branch to the [2.0.0-beta branch|https://github.com/jenkinsci/git-client-plugin/commits/2.0.0-beta]. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://g
[JIRA] (JENKINS-37188) 2nd failure emails being sent even when build is successful with job-dsl-plugin
Title: Message Title David van Laatum commented on JENKINS-37188 Re: 2nd failure emails being sent even when build is successful with job-dsl-plugin That was done rather poorly 1) It was using a class variable that didn't follow the correct data bound pattern 2) It's checking for the nth failure after a success so 3 failures in a row the second will trigger the email but the third will not Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Sam Gleske commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated Thanks for the update, Mark. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37188) 2nd failure emails being sent even when build is successful with job-dsl-plugin
Title: Message Title David van Laatum updated an issue Jenkins / JENKINS-37188 2nd failure emails being sent even when build is successful with job-dsl-plugin Change By: David van Laatum Component/s: job-dsl-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37188) 2nd failure emails being sent even when build is successful with job-dsl-plugin
Title: Message Title David van Laatum updated an issue Jenkins / JENKINS-37188 2nd failure emails being sent even when build is successful with job-dsl-plugin Change By: David van Laatum Summary: 2nd failure emails being sent even when build is successful with job-dsl-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-6918) optionalBlock tag is not initialized correctly when declared within a radioBlock
Title: Message Title Guillaume DELORY commented on JENKINS-6918 Re: optionalBlock tag is not initialized correctly when declared within a radioBlock Hi Vincent, not sure you're still around after so much time, but I'm facing the same issue. If anyone is facing the same issue, I will probably post a fix here soon in a first time, then hopefully I will contribute this back once I have all necessary approvals. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31939) The top value is better to be chosen by default of to have such option
Title: Message Title Boguslaw Klimas resolved as Fixed release 0.6.2 Jenkins / JENKINS-31939 The top value is better to be chosen by default of to have such option Change By: Boguslaw Klimas Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36934) No return value passed to the url
Title: Message Title Boguslaw Klimas resolved as Fixed release 0.6.2 Jenkins / JENKINS-36934 No return value passed to the url Change By: Boguslaw Klimas Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36833) Race Condition Populating Multiple Tag Parameters
Title: Message Title Boguslaw Klimas resolved as Fixed release 0.6.2 Jenkins / JENKINS-36833 Race Condition Populating Multiple Tag Parameters Change By: Boguslaw Klimas Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36833) Race Condition Populating Multiple Tag Parameters
Title: Message Title Boguslaw Klimas stopped work on JENKINS-36833 Change By: Boguslaw Klimas Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Yevhenii Kurtov commented on JENKINS-33841 Re: Support for pipeline builds Hello Itai Sanders I notice that you have a status notification message in the logs Sending build status INPROGRESS for commit 4e7eb185a08b8b5cb1775c31d26f3f05cbaa8bbc to BitBucket is done! Sending build status SUCCESSFUL for commit 4e7eb185a08b8b5cb1775c31d26f3f05cbaa8bbc to BitBucket is done! what looks really good, but my build doesn't issue even anything close to that, I have just: Proceeding [Pipeline] bitbucketStatusNotify [Pipeline] stage (Checkout) and even more strange - error in the end [Pipeline] bitbucketStatusNotify [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline java.lang.NullPointerException at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifierStep$Execution.run(BitbucketBuildStatusNotifierStep.java:191) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifierStep$Execution.run(BitbucketBuildStatusNotifierStep.java:140) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:213) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Finished: FAILURE Can you please suggest what I might be missing? The only difference I can see between my and sample config is that I'm fetching code with credentials: checkout([$class: 'GitSCM', branches: [[name: env.BRANCH_NAME]], doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [], userRemoteConfigs: [[credentialsId: 'c6bcc00a-8dea-4671-bdd3-8335a959d610', url: 'g...@bitbucket.xxx/xxx.git']]])
[JIRA] (JENKINS-34958) Getting "Your Authorization Token has expired" when using ECR credentials
Title: Message Title
Joseph Orilogbon edited a comment on JENKINS-34958
Re: Getting "Your Authorization Token has expired" when using ECR credentials
I created a PR for this issue here:https://github.com/jenkinsci/amazon-ecr-plugin/pull/6I added a new credential format that contains the region. For example, by specifying the following credentials: ` {{ ecr:us-west-2:credential-id ` }} , the provider will set the Region of the AWS Client to ` {{ us-west-2 ` }} , when requesting for Authorisation token.The current credential format is supported and uses the default region (us-east-1) specified in [AmazonECRClient](https://github.com/aws/aws-sdk-java/blob/5ec8907a0342bff23e15fc290f715c66cb9bad03/aws-java-sdk-ecr/src/main/java/com/amazonaws/services/ecr/AmazonECRClient.java#L338)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34958) Getting "Your Authorization Token has expired" when using ECR credentials
Title: Message Title Joseph Orilogbon commented on JENKINS-34958 Re: Getting "Your Authorization Token has expired" when using ECR credentials I created a PR for this issue here: https://github.com/jenkinsci/amazon-ecr-plugin/pull/6 I added a new credential format that contains the region. For example, by specifying the following credentials: `ecr:us-west-2:credential-id`, the provider will set the Region of the AWS Client to `us-west-2`, when requesting for Authorisation token. The current credential format is supported and uses the default region (us-east-1) specified in [AmazonECRClient](https://github.com/aws/aws-sdk-java/blob/5ec8907a0342bff23e15fc290f715c66cb9bad03/aws-java-sdk-ecr/src/main/java/com/amazonaws/services/ecr/AmazonECRClient.java#L338) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Ben Place commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated @Mark Waite, your suggestion to me on 19 April worked. Thank you. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31487) Job status not updated in web UI during build
Title: Message Title Daniel Beck commented on JENKINS-31487 Re: Job status not updated in web UI during build Gerard CK You're saying it's broken in 1.625.3 as well? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22547) Git timeout setting does not work for checkout
Title: Message Title Mark Waite commented on JENKINS-22547 Re: Git timeout setting does not work for checkout Quentin Dufour's fix will be in the git client plugin 1.19.8 release Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37185) Checkout timeout is not honored when used with local branch parameter
Title: Message Title Mark Waite commented on JENKINS-37185 Re: Checkout timeout is not honored when used with local branch parameter Fix will be in the git-client-plugin 1.19.8 release Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37235) Simplify rendering of the stages table, to template cleanly off of the runs
Title: Message Title Sam Van Oort created an issue Jenkins / JENKINS-37235 Simplify rendering of the stages table, to template cleanly off of the runs Issue Type: Improvement Assignee: Sam Van Oort Components: pipeline-stage-view-plugin Created: 2016/Aug/06 3:40 PM Labels: user-experience Priority: Minor Reporter: Sam Van Oort Currently rendering is overly complex due to the async loading of individual stage data for runs. This can be refactored to be simpler and use more direct templating, which makes JENKINS-33185 easier to execute. Don't cache/request individual stages, instead use the runs table (already stored) and NEVER issues requests for individual stages. Refactor tests dependent on the stage/run separation Pull out the stuff that fetches stage descriptions (probably for popups) and tie it to initial templating with run data. Add full stage data to JS test cases
[JIRA] (JENKINS-37234) Stage view fetches one extra run when supplying a "since" parameter
Title: Message Title Sam Van Oort created an issue Jenkins / JENKINS-37234 Stage view fetches one extra run when supplying a "since" parameter Issue Type: Improvement Assignee: Sam Van Oort Components: pipeline-stage-view-plugin Created: 2016/Aug/06 3:27 PM Labels: performance Priority: Minor Reporter: Sam Van Oort When fetching updated runs since the last fetch cycle, the /runs API will fetch the run matching the "since" parameter, not just ones after that. This means extra data is sent every time. Trivial change here: https://github.com/jenkinsci/pipeline-stage-view-plugin/blob/master/rest-api/src/main/java/com/cloudbees/workflow/rest/external/JobExt.java#L121 The catch is we need to ensure tests handle this correctly, and the UI does too. Possible issues of API compat, but I think likely safe. Add Comment
[JIRA] (JENKINS-36865) Stage view showing wrong pipeline data
Title: Message Title Sam Van Oort updated JENKINS-36865 Released with v1.7 Jenkins / JENKINS-36865 Stage view showing wrong pipeline data Change By: Sam Van Oort Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37001) unstable pipelines have their build# icon rendered in blue not yello.
Title: Message Title Sam Van Oort closed an issue as Fixed Released with v1.7 Jenkins / JENKINS-37001 unstable pipelines have their build# icon rendered in blue not yello. Change By: Sam Van Oort Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34036) Stage view issues many more requests than needed
Title: Message Title Sam Van Oort updated JENKINS-34036 Released with version 1.7 Jenkins / JENKINS-34036 Stage view issues many more requests than needed Change By: Sam Van Oort Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37188) 2nd failure emails being sent even when build is successful
Title: Message Title Marc Esher commented on JENKINS-37188 Re: 2nd failure emails being sent even when build is successful Hi David, I believe I've gotten to the bottom of this. I'm not sure what the exact right fix is, because it seems there might be several. Bear with me, this might take a while: We use job-dsl-plugin to configure our jobs. And when I added a secondFailure trigger via job-dsl-plugin, that's when I observed the behavior I described. If I then re-saved the job in the Jenkins UI, the problem went away. This led me to investigate the difference in config.xml between the job-dsl generated version and the JenkinsUI generated version, and it was this: in the job-dsl generated job, I saw: "0" for the SecondFailureTrigger element. But in the Jenkins UI generated job, I saw "2" for the SecondFailureTrigger element. I then added some debugging to the email-ext and uploaded, and saw that in https://github.com/jenkinsci/email-ext-plugin/blob/master/src/main/java/hudson/plugins/emailext/plugins/trigger/NthFailureTrigger.java#L35-L53, because failureCount was 0, then that entire loop was skipped, and it'd hit the last line: return run == null || run.getResult() == Result.SUCCESS || run.getResult() == Result.UNSTABLE; And since the result was SUCCESS, it'd return true, and the email would get triggered. So there are 2 problems: 1) for some reason, the job-dsl version generates a failureCount of 0, which causes the for loop to get skipped 2) the return seems, to me, to have incorrect logic. I can't figure out why it'd return true if the result was SUCCESS. So to fix this, I noticed that FirstFailureTrigger has a readResolve() block that seems to cover this exact condition. Thus, I added a readResolve() block to SecondFailureTrigger, just replacing "1" with "2" Re-uploaded the plugin, and that fixed everything. So to me, that seems like a sensible fix and I'm happy to submit a PR if you think that's correct. Still, though, that return in trigger() seems off to me, so you probably want to check that out. If you think the logic should be Result.FAILURE instead of Result.SUCCESS, let me know and I can add that to the PR Add Comment
[JIRA] (JENKINS-27120) Make JacocoPublisher a SimpleBuildStep
Title: Message Title Brian St.Clair commented on JENKINS-27120 Re: Make JacocoPublisher a SimpleBuildStep Thanks! I'll give mheinzerling_2.1.0 a shot and let you know if I run into any issues. Much appreciated. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37232) ATH test fails on NEW ITEM Wizard on Jenkins 2.7
Title: Message Title Manuel Recena Soto commented on JENKINS-37232 Re: ATH test fails on NEW ITEM Wizard on Jenkins 2.7 valentina armenise Sure, but after more changes were introduced (ref). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37232) ATH test fails on NEW ITEM Wizard on Jenkins 2.7
Title: Message Title
Manuel Recena Soto updated an issue
Jenkins / JENKINS-37232
ATH test fails on NEW ITEM Wizard on Jenkins 2.7
Change By:
Manuel Recena Soto
When running ATH tests agains Jenkins 2.7 the New Item Wizard fails to enable the OK button after the name is inserted and the type of item selected.Some investigation and debugging showed that: 1) # the item name is inserted and stored with jquery, no warning shown. Validation of OK button fails cause the item time has not been selected yet (OK button not shown yet). 2) # the item type is selected 3) # right after selecting the item type a red warning is show on the item name input text ("The field cannot be empty, please enter a valid name") 3) # the OK button is not shown case now the validation fails on the item name (empty).If while debugging, you click anywhere on the page after the item type is selected, the red warning goes away and the OK button shown. Sending Keys.TAB with selenium (or changing focus) does not work instead.Looks like this condition is false https://github.com/jenkinsci/jenkins/blob/5f9614433ec3bd9057097bbe2af7d445e6cd918e/war/src/main/js/add-item.js#L178.The ATH tests are failing here https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/main/java/org/jenkinsci/test/acceptance/po/JobsMixIn.java#L25
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-31487) Job status not updated in web UI during build
Title: Message Title Gerard CK commented on JENKINS-31487 Re: Job status not updated in web UI during build Hi Daniel, The last version that has a working build progress bar is 1.625.2 The progress bar is broken in every versions after that. Cheers Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35310) "Trigger builds remotely" doesn't save authToken
Title: Message Title Mickaël Perrin commented on JENKINS-35310 Re: "Trigger builds remotely" doesn't save authToken Can confirm the issue, really annoying. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37233) Switch to a responsive table component
Title: Message Title James Dumay created an issue Jenkins / JENKINS-37233 Switch to a responsive table component Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2016/Aug/06 8:45 AM Priority: Minor Reporter: James Dumay This looks pretty excellent and we will want this kind of functionality https://facebook.github.io/fixed-data-table/example-filter.html Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
