[JIRA] (JENKINS-39654) HP_RUN_ID not available after Jenkins security change
Title: Message Title John Gregg commented on JENKINS-39654 Re: HP_RUN_ID not available after Jenkins security change I'm using 5.6.2 and still see the same behavior. I don't see anything in the committed files that looks like it addresses this problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176222.1478804911000.219.1563994500271%40Atlassian.JIRA.
[JIRA] (JENKINS-42476) PC client exits too soon
Title: Message Title John Gregg commented on JENKINS-42476 Re: PC client exits too soon Sorry it took so long. I don't have the permissions to do the update myself. We did finally update to 5.0.1 and have had a number of successful builds without any failures, so I think this issue can be closed. Thanks Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-42476) PC client exits too soon
Title: Message Title John Gregg updated an issue Jenkins / JENKINS-42476 PC client exits too soon Change By: John Gregg Summary: PC client exists exits too soon 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-42476) PC client exists too soon
Title: Message Title John Gregg created an issue Jenkins / JENKINS-42476 PC client exists too soon Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 2017/Mar/03 5:22 PM Environment: Jenkins 2.19.4 HP plugin version 4.0.1 Priority: Minor Reporter: John Gregg Frequently my HP plugin exits before the load test is actually done. This causes some of my post-run scripts to fail. My job is configured to collate and analyze. I noticed a difference in the plugin output between a successful an unsuccessful run. Unsuccessful: Run started (TestID: 4802, RunID: 6790, TimeslotID: 4276) Set HP_RUN_ID Env Variable to 6790 RunID: 6790 - State = Initializing RunID: 6790 - State = Running RunID: 6790 - State = Stopping View report: http://myserver:8080/job/myjob/153/artifact/performanceTestsReports/pcRun6790/Report.html Logout succeeded Result Status (PC RunID: 6790): SUCCESS Successful: Run started (TestID: 4802, RunID: 6796, TimeslotID: 4297) Set HP_RUN_ID Env Variable to 6796 RunID: 6796 - State = Initializing RunID: 6796 - State = Running RunID: 6796 - State = Collating Results RunID: 6796 - State = Creating Analysis Data RunID: 6796 - State = Finished Publishing run report View report: http://myserver:8080/job/myjob/154/artifact/performanceTestsReports/pcRun6796/Report.html Logout succeeded Result Status (PC RunID: 6796): SUCCESS Notice how the last state of the successful one is "Finished?" The unsuccessful one doesn't even show the collate and analyze steps. This seems to be a pretty clear pattern across multiple executions. thanks
[JIRA] (JENKINS-34821) HP_RUN_ID not available in parameterized builds
Title: Message Title John Gregg commented on JENKINS-34821 Re: HP_RUN_ID not available in parameterized builds I don't think these are the same. I can think of a couple of ways to test: For NON-parameterized builds, is HP_RUN_ID available after the build step completes without the security workaround in JENKINS-39654? For parameterized builds, is HP_RUN_ID available after the build step completes with the security workaround in JENKINS-39654? I think the two things are unrelated. thanks 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-35097) Support passing command line parameters to test scenario
Title: Message Title John Gregg commented on JENKINS-35097 Re: Support passing command line parameters to test scenario Different AUT servers. I use the "command line" in the scenario when I run tests manually. However in this case I want to pass the value through the plugin to the scenario. I know you use the REST API under the covers but I don't think it supports this so it would need to be tweaked. Thanks 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-39654) HP_RUN_ID not available after Jenkins security change
Title: Message Title John Gregg commented on JENKINS-39654 Re: HP_RUN_ID not available after Jenkins security change I only have experience with performance tests. I use the build step "Execute HP tests using Performance Center." The plugin tries to set an environment variable called HP_RUN_ID in PcBuilder.java. That parameter is no longer visible once the plugin completes its work because of the security restriction in the link I provided unless we follow the workarounds. I'm hoping you can do something to make this work again without needing a workaround. See the link for information. I personally pass the HP_RUN_ID to Ant scripts to do various things. The attached file jenkins-bad.txt shows the results of running a test, followed by a post-build step to execute a Windows batch command. In this case I'm just echoing %HP_RUN_ID%, which you can see is empty. I no longer have an installed old copy of Jenkins to test the previous behavior, but jenkins-good.txt shows what happens when I use one of the workarounds in the security note. Thanks 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-39654) HP_RUN_ID not available after Jenkins security change
Title: Message Title John Gregg updated an issue Jenkins / JENKINS-39654 HP_RUN_ID not available after Jenkins security change Change By: John Gregg Attachment: jenkins-bad.txt 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-39654) HP_RUN_ID not available after Jenkins security change
Title: Message Title John Gregg updated an issue Jenkins / JENKINS-39654 HP_RUN_ID not available after Jenkins security change Change By: John Gregg Attachment: jenkins-good.txt 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-39654) HP_RUN_ID not available after Jenkins security change
Title: Message Title John Gregg created an issue Jenkins / JENKINS-39654 HP_RUN_ID not available after Jenkins security change Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 2016/Nov/10 7:08 PM Priority: Blocker Reporter: John Gregg https://jenkins.io/blog/2016/05/11/security-update/ This security update prevents me from accessing HP_RUN_ID after the build has executed. thanks Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-34456) Image Gallery Plugin does not play nice with XML-Summary Report plugin
Title: Message Title John Gregg commented on JENKINS-34456 Re: Image Gallery Plugin does not play nice with XML-Summary Report plugin Not 100% sure my issue is the same, but I also use both of these plugins. They both use _javascript_. The Firefox debugger says "TypeError: jQuery(...).colorbox is not a function." In my case, the images do not appear on the build summary page. I can click into the build artifacts directory and see links to my images, however. thanks 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] [hp-application-automation-tools-plugin] (JENKINS-35097) Support passing command line parameters to test scenario
Title: Message Title John Gregg created an issue Jenkins / JENKINS-35097 Support passing command line parameters to test scenario Issue Type: Improvement Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 2016/May/24 2:31 PM Priority: Minor Reporter: John Gregg I need the ability to run the same test scenario against different servers. Currently I use command line parameters to change the endpoint of my scripts in Performance Center. I need to be able to pass those parameters through the plugin also. Thanks. Add Comment
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-34821) HP_RUN_ID not available in parameterized builds
Title: Message Title John Gregg created an issue Jenkins / JENKINS-34821 HP_RUN_ID not available in parameterized builds Issue Type: Bug Assignee: Ofir Shaked Attachments: hp.patch Components: hp-application-automation-tools-plugin Created: 2016/May/13 6:58 PM Priority: Major Reporter: John Gregg Setting HP_RUN_ID only works if the build is not parameterized. If it is parameterized, HP_RUN_ID does not get passed to subsequent Ant scripts. For it to work with parameterized builds also, you need to check for existing string parameters, merge in the new one, and replace the existing parameters. See the attached patch for a fix. thanks Add Comment
