[JIRA] (JENKINS-59971) Unable to create folder credentials for plain-credentials-plugin
Title: Message Title
Jason Swager edited a comment on JENKINS-59971
Re: Unable to create folder credentials for plain-credentials-plugin
[~rittneje] - perhaps this will help. Your original example helped me get much further; I couldn't have figured out the secret file stuff without your example.{code:java}properties { folderCredentialsProperty {domainCredentials { domainCredentials {domain { name('') description('')} }} }}configure { folder -> def configNode = folder / 'properties' / 'com.cloudbees.hudson.plugins.folder.properties.FolderCredentialsProvider_-FolderCredentialsProperty' / 'domainCredentialsMap' / 'entry' / 'java.util.concurrent.CopyOnWriteArrayList' configNode << 'org.jenkinsci.plugins.plaincredentials.impl.FileCredentialsImpl' {id('secret-file-id')description('secret file desc')fileName('test.txt')secretBytes(com.cloudbees.plugins.credentials.SecretBytes.fromBytes('''This is a multiline fileLine two finaly final line'''.getBytes()).toString()) }}{code}This example won't work with a binary file. If that was necessary, you could generate a BASE64 encode of the binary file, put that in place of the string and do a decodeBase64() on it to get the bytes.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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
[JIRA] (JENKINS-59971) Unable to create folder credentials for plain-credentials-plugin
Title: Message Title
Jason Swager commented on JENKINS-59971
Re: Unable to create folder credentials for plain-credentials-plugin
Jesse Rittner - perhaps this will help. Your original example helped me get much further; I couldn't have figured out the secret file stuff without your example.
properties {
folderCredentialsProperty {
domainCredentials {
domainCredentials {
domain {
name('')
description('')
}
}
}
}
}
configure { folder ->
def configNode = folder / 'properties' / 'com.cloudbees.hudson.plugins.folder.properties.FolderCredentialsProvider_-FolderCredentialsProperty' / 'domainCredentialsMap' / 'entry' / 'java.util.concurrent.CopyOnWriteArrayList'
configNode << 'org.jenkinsci.plugins.plaincredentials.impl.FileCredentialsImpl' {
id('secret-file-id')
description('secret file desc')
fileName('test.txt')
secretBytes(com.cloudbees.plugins.credentials.SecretBytes.fromBytes('''This is a multiline file
Line two
finaly line'''.getBytes()).toString())
}
}
This example won't work with a binary file. If that was necessary, you could generate a BASE64 encode of the binary file, put that in place of the string and do a decodeBase64() on it to get the bytes.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this
[JIRA] (JENKINS-56669) Sort builds chronologically
Title: Message Title Jason Swager commented on JENKINS-56669 Re: Sort builds chronologically I like that there's no configuration too! Just straight forward clean and simple. I was thinking maybe more a radio button on the rendered page: Sort by: Name | Start Time. Or maybe a drop down box. The user select which one at view time. No job or system configuration. The Timestamper plugin has something like this; on every console output page, they have the radio buttons to show timestamps as UTC time/local time, or time elapsed. No configuration, no XML file, just the user's choice when they view the page. I think the choice is stored in a cookie, so when you go to another console page, it remembers your last selection. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56669) Sort builds chronologically
Title: Message Title Jason Swager created an issue Jenkins / JENKINS-56669 Sort builds chronologically Issue Type: Improvement Assignee: Gustaf Lundh Components: yet-another-build-visualizer-plugin Created: 2019-03-21 20:34 Environment: Ubuntu 16.04 Jenkins 2.150.3.2 Rolling Yet Another Build Visualizer: v1.5 Priority: Minor Reporter: Jason Swager Our users are very impressed with this plugin and it's ability to quickly visualize our mess of upstream and downstream jobs. In our pipelines, we often call the same job several times - different parameters - so it appears multiple times in the diagram. Not a bad thing; they're all nicely sorted alphabetically. But for our use case, if they were sorted chronologically, that would better help finding the specific job. I don't know which would be easier to implement - a global setting or a setting on the display page itself, where a user could toggle back and forth. Add Comment
[JIRA] (JENKINS-48490) Intermittently slow docker provisioning with no errors
Title: Message Title Jason Swager commented on JENKINS-48490 Re: Intermittently slow docker provisioning with no errors We are seeing similar symptoms after upgrading the Docker plugin. Our Jenkins masters started seeing this problem after upgrading to Docker Plugin v1.1.1 and even v1.1.2. One big difference, we're using SSH to connect rather than JNLP. The larger and more busy the Jenkins master, the faster this problem occurs. Our larger one we had to downgrade the Docker plugin to it's prior version, 0.16.2. The smaller Jenkins don't suffer immediately from the problem and a restart of them clears the problem - at least for another couple days. 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-41274) "Run as Specific User" does not work with Pipeline Jobs
Title: Message Title
Jason Swager created an issue
Jenkins / JENKINS-41274
"Run as Specific User" does not work with Pipeline Jobs
Issue Type:
Bug
Assignee:
Unassigned
Components:
authorize-project-plugin, pipeline
Created:
2017/Jan/21 5:22 AM
Environment:
Jenkins ver. 1.651.21.1 (CloudBees Jenkins Enterprise 16.06) Ubuntu 14.04 Authorize Project 1.2.2 Pipeline 2.4
Priority:
Critical
Reporter:
Jason Swager
When using a Jenkins Pipeline job and "Configure Build Authorization" is enabled to "Run as Specific Use" and a valid user is filled in, the job is not run as the specified user. It is always run as the user that ran the job. When using the same settings, but using a FreeStyle job, the job is run as the specified user. Notably, the line "Running as {user name} " is showing in the console log.
Add Comment
[JIRA] (JENKINS-31396) Access to submitter ID from return value of input step
Title: Message Title Jason Swager commented on JENKINS-31396 Re: Access to submitter ID from return value of input step Submitted https://github.com/jenkinsci/pipeline-input-step-plugin/pull/8 to address this, because I want the feature too. Just not sure what the process is of getting a code review performed and getting it merged. 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] [pagerduty-plugin] (JENKINS-35353) PagerDuty plugin not compatible with Pipeline plugin
Title: Message Title Jason Swager commented on JENKINS-35353 Re: PagerDuty plugin not compatible with Pipeline plugin We use a combination of Freestyle jobs and Pipeline (used to be called WorkFlow) jobs. Pipeline jobs are described here: https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin. For the FreeStyle jobs, the PagerDuty plugin is easily accessible as a PostBuild step. But for the Pipeline jobs, where the job is mostly described as Groovy script, the PagerDuty plugin is not accessible. This guide appears to show how to modify the plugin to be accessible by both FreeStyle and Pipeline jobs: https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md#build-wrappers< /p> Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pagerduty-plugin] (JENKINS-35353) PagerDuty plugin not compatible with Pipeline plugin
Title: Message Title Jason Swager created an issue Jenkins / JENKINS-35353 PagerDuty plugin not compatible with Pipeline plugin Issue Type: Improvement Assignee: Alexander Leibzon Components: pagerduty-plugin Created: 2016/Jun/03 11:23 PM Environment: PagerDuty Plugin 0.2.4 Jenkins 1.651.1 Priority: Major Reporter: Jason Swager The PagerDuty Plugin is rather nice and works well from a FreeStyle job. Could it also be made to work from a Pipeline Job? Add Comment
[JIRA] [label-linked-jobs-plugin] (JENKINS-32445) Make Label Linked Jobs plugin compatible with Jenkins Clouds definition
Title: Message Title Jason Swager commented on JENKINS-32445 Re: Make Label Linked Jobs plugin compatible with Jenkins Clouds definition Dominique Brice - sorry for the delay in response. Yes, I do have a sandbox instance where I can try out these changes. I loaded the snapshot version of the plugin and it worked rather well. Instead of seeing jobs that appear orphaned because they linked to labels on cloud providers, they now report the number of clouds and which ones can support them. This looks like a successful feature implementation to me! Thanks much! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cli] (JENKINS-11024) Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others
Title: Message Title Jason Swager commented on JENKINS-11024 Re: Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others Sorry - this is my mistake. This doens't involve the ssh keys, just a normal username/password login. Please close this issue and I'll open a different one. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cli] (JENKINS-11024) Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others
Title: Message Title
Jason Swager edited a comment on JENKINS-11024
Re: Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others
Apologies, [~danielbeck], let me add the bare minimum reproduce steps.# I installed a fresh Jenkins via it's docker container. The version it had was 1.642.2.# Once running and connected, added the Folder Plugin and the Role-based Authorization Strategy (in my production scenario, we're using CloudBees Roles and Groups - but this one will suffice)# Enable security via Manage Jenkins -> Global Security: Jenkins own database, allow users to sign-up, Role-Based Strategy. # Create yourself as a user and sign in as yourself# Under Manage Jenkins -> Manage and Assign Roles: Under Manage Roles, make sure "admin" role has access to everything. Under Assign Roles, remove "Anonymous" group from "admin", add yourself and give access to "admin" role.# Back at Jenkins main page, create a Folder (via New Item -> Folder) called "alpha"# In Folder "alpha" create a simple Freestyle Job called "test-job", make it do something - whatever. No parameters is easiest.Now for the command line work (command may be slightly incorrect; typing from memory here) - replace JENKINS_URL and userid as appropriate :# At the command line, get the jenkins-cli: {{ curl -o jenkins-cli { JENKINS_URL } /jnlpJars/jenkins-cli.jar }} # Make it easy - login as you: {{ java -jar jenkins-cli.jar -s { JENKINS_URL } login --username {your user}}} userid # Verify you can see the alpha folder: {{ java -jar jenkins-cli.jar -s { JENKINS_URL } list-jobs }} # Verify you can see the test-job job: {{ java -jar jenkins-cli.jar -s { JENKINS_URL } list-jobs alpha }} # Try to run test-job: {{ java -jar jenkins-cli.jar -s { JENKINS_URL } build alpha/test-job }} # I get the following when I try: {{ $ java -jar jenkins-cli.jar -s http://192.168.99.100:8080 build "alpha/test-job"No such job 'alpha/test-job' }}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop
[JIRA] [cli] (JENKINS-11024) Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others
Title: Message Title
Jason Swager commented on JENKINS-11024
Re: Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others
Apologies, Daniel Beck, let me add the bare minimum reproduce steps.
I installed a fresh Jenkins via it's docker container. The version it had was 1.642.2.
Once running and connected, added the Folder Plugin and the Role-based Authorization Strategy (in my production scenario, we're using CloudBees Roles and Groups - but this one will suffice)
Enable security via Manage Jenkins -> Global Security: Jenkins own database, allow users to sign-up, Role-Based Strategy.
Create yourself as a user and sign in as yourself
Under Manage Jenkins -> Manage and Assign Roles: Under Manage Roles, make sure "admin" role has access to everything. Under Assign Roles, remove "Anonymous" group from "admin", add yourself and give access to "admin" role.
Back at Jenkins main page, create a Folder (via New Item -> Folder) called "alpha"
In Folder "alpha" create a simple Freestyle Job called "test-job", make it do something - whatever. No parameters is easiest.
Now for the command line work (command may be slightly incorrect; typing from memory here):
At the command line, get the jenkins-cli: {{curl -o jenkins-cli {JENKINS_URL}/jnlpJars/jenkins-cli.jar}} # Make it easy - login as you: {{java -jar jenkins-cli.jar -s {JENKINS_URL}
login --username {your user}
}}
Verify you can see the alpha folder: {{java -jar jenkins-cli.jar -s {JENKINS_URL} list-jobs}} # Verify you can see the test-job job: {{java -jar jenkins-cli.jar -s {JENKINS_URL}
list-jobs alpha}}
Try to run test-job: {{java -jar jenkins-cli.jar -s {JENKINS_URL}
build alpha/test-job}}
I get the following when I try: {{ $ java -jar jenkins-cli.jar -s http://192.168.99.100:8080 build "alpha/test-job" No such job 'alpha/test-job' }}
[JIRA] [cli] (JENKINS-11024) Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others
Title: Message Title Jason Swager reopened an issue It's reproducible! Jenkins / JENKINS-11024 Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others Change By: Jason Swager Resolution: Cannot Reproduce Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cli] (JENKINS-11024) Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others
Title: Message Title Jason Swager commented on JENKINS-11024 Re: Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others I'm experiencing this problem. Using CloudBees folders and roles/groups with absolutely no permissions for non-authenticated users. I can list-job through the folders and see the job. But trying to build it via the cli results in "ERROR: No such job" Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-32480) Continuous integration using Jenkins Workflow and Validated Merge
Title: Message Title Jason Swager commented on JENKINS-32480 Re: Continuous integration using Jenkins Workflow and Validated Merge Ran into the same issue and have the same question. Just finished converting some non-validated merge pipelines to Workflow/Pipeline and their teams are highly impressed at the results. Now the Validated Merge pipeline teams are drooling to have the same coolness... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [label-linked-jobs-plugin] (JENKINS-32445) Make Label Linked Jobs plugin compatible with Jenkins Clouds definition
Title: Message Title Jason Swager commented on JENKINS-32445 Re: Make Label Linked Jobs plugin compatible with Jenkins Clouds definition You are correct, this really is a feature - not a bug. I'm not sure if this would work, but perhaps for every label or combination of labels that the Linked Jobs plugin is processing, it could do a canProvision() on that label against each Cloud instance that's currently registered in Jenkins. If a Cloud responds affirmative, then the dashboard could just note the Clouds that support that combination. The dashboard wouldn't be able to tell how many nodes would support the label combination in that particular Cloud, but it would at least know that it can be handled. This logic could be used to determine if orphan jobs (jobs that have no runnable node) are really orphans or if some cloud can support them. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [label-linked-jobs-plugin] (JENKINS-32445) Temporary slaves aren't counted
Title: Message Title Jason Swager created an issue Jenkins / JENKINS-32445 Temporary slaves aren't counted Issue Type: Bug Assignee: Dominique Brice Components: label-linked-jobs-plugin Created: 14/Jan/16 2:33 AM Environment: Jenkins 1.6253, Label Linked Jobs 4.0.3, Docker Plugin 0.16.0 Labels: jenkins plugin labels docker Priority: Minor Reporter: Jason Swager With fixed slaves, Label Linked Jobs dashboard shows available labels and the jobs associated with them correctly. But when slaves are temporary - created on-demand when a job starts, then destroyed when the job is complete - those labels do not appear in the Label Linked Jobs dashboard. For example, the Docker Plugin allows creating a "cloud" where the "cloud" contains slaves that will be created from docker containers on demand. Each slave does have a label string associated with, just like a normal slave. Not sure if the Jenkins generic cloud has a way of getting the labels or not. There are other plugins
[JIRA] [promoted-builds-plugin] (JENKINS-32006) Promoted Builds Plugin tries to fetch changes from Git
Title: Message Title Jason Swager commented on JENKINS-32006 Re: Promoted Builds Plugin tries to fetch changes from Git Same thing happened to me. It's rather annoying, since it pollutes the workspace of the promotion. The problem becomes show stopper when the GIT SCM of the original job uses a specific credential to clone from the repo. The promotion gets the repo information, but not the credential, so the clone fails. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [vsphere-cloud-plugin] (JENKINS-25955) Restart (and revert) Guest before build
Title: Message Title Jason Swager commented on JENKINS-25955 Re: Restart (and revert) Guest before build Would the following solution work? Assumptions: Disable the slave's revert after X builds feature. As either the first build steps, or as a job that runs prior to your list of build steps, do the following - must be done from a slave OTHER than the target VM slave: Power on target VM slave if necessary. Execute a job on the target VM slave - update the software as necessary. Power the target VM slave down (may need to use the Jenkins CLI to temporarily disable the slave to prevent Jenkins from restarting it once powered down) Take a new snapshot, delete the old revert snapshot. (If necessary, enable the slave via Jenkins CLI), power on the target VM slave Run your normal build steps or job with those build steps Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [vsphere-cloud-plugin] (JENKINS-25955) Restart (and revert) Guest before build
Title: Message Title Jason Swager commented on JENKINS-25955 Re: Restart (and revert) Guest before build That's the problem. I can't touch the slave once the job begins. Jenkins will only allow the job to run on a slave if the slave is running and can take the job. If the job starts running on the slave and the slave does a revert, the Jenkins-slave connection is broken and Jenkins will abort the slave. I tried a feature like this early on, but it won't work with Jenkins. Only at the end of the job - when the job is no longer running on the slave, can the plugin do something drastic like revert the VM. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [vsphere-cloud-plugin] (JENKINS-25955) Restart (and clean) Guest before build
Title: Message Title Jason Swager commented on JENKINS-25955 Re: Restart (and clean) Guest before build From the perspective of a slave, there is no mechanism that can be used to clean a slave between runs of a job. The closest feature that the vSphere Plugin has is the ability to run a specific number of jobs, then revert the VM back to a snapshot. Because clean is ambiguous (remove files, directories, restore files to original state, stop services/processes, run database commands), this sort of logic in a slave plugin is probably not the right place for it. One possible solution: if you have a job that is supposed to run on the slave and needs to be cleaned up after, use either the PostBuild step to clean it up. Or move the cleanup logic to a separate job that gets run immediately after your own job. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [vsphere-cloud-plugin] (JENKINS-25955) Restart (and revert) Guest before build
Title: Message Title Jason Swager commented on JENKINS-25955 Re: Restart (and revert) Guest before build Reverting to a snapshot after X builds is a feature of the vSphere Plugin. Have you tried it? Does it work for you? I've seen uses of the plugin - particularly the build step parts for creating/deleting snapshots - where a Job is run to update the slave with new software, then a new snapshot. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [poll-mailbox-trigger-plugin] (JENKINS-27575) Please add possibility to handle the attachment of mail to this plugin
Jason Swager commented on JENKINS-27575 Please add possibility to handle the attachment of mail to this plugin I think this would be a very nice feature as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [promoted-builds-plugin] (JENKINS-26819) Allow a previous build to be promoted while new build is in progress
Jason Swager commented on JENKINS-26819 Allow a previous build to be promoted while new build is in progress I've observed the same behavior - and have the same request. Can a promotion not block the job from running? And the job not block a promotion? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud-plugin] (JENKINS-25588) Integrate vSphere Cloud plugin with Credentials plugin (auth options)
Jason Swager resolved JENKINS-25588 as Fixed Integrate vSphere Cloud plugin with Credentials plugin (auth options) Should be resolved in v2.1 Change By: Jason Swager (06/Jan/15 3:56 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud-plugin] (JENKINS-25588) Integrate vSphere Cloud plugin with Credentials plugin (auth options)
Jason Swager resolved JENKINS-25588 as Fixed Integrate vSphere Cloud plugin with Credentials plugin (auth options) v2.0 Change By: Jason Swager (24/Dec/14 7:23 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-23775) Shutdown of VM after Inactivity Failed
Jason Swager resolved JENKINS-23775 as Fixed Shutdown of VM after Inactivity Failed Resolved by the v1.1.12 changes. Change By: Jason Swager (06/Oct/14 7:50 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-23775) Shutdown of VM after Inactivity Failed
Jason Swager commented on JENKINS-23775 Shutdown of VM after Inactivity Failed Will close by Oct 13 if no further comments from the submitter. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-23775) Shutdown of VM after Inactivity Failed
Jason Swager assigned JENKINS-23775 to Jason Swager Shutdown of VM after Inactivity Failed Change By: Jason Swager (01/Sep/14 3:21 AM) Assignee: JasonSwager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-24479) The vSphere cloud will not allow this slave to start at this time.
Jason Swager assigned JENKINS-24479 to Jason Swager The vSphere cloud will not allow this slave to start at this time. Change By: Jason Swager (01/Sep/14 3:21 AM) Assignee: JasonSwager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-21647) In Vsphere Cloud I can not create a machine from a template
Jason Swager resolved JENKINS-21647 as Fixed In Vsphere Cloud I can not create a machine from a template If no resource pool is specified, the default Resources will be used. Change By: Jason Swager (08/Jul/14 2:23 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-23212) Option Delay between launch and boot complete doesn't work
Jason Swager commented on JENKINS-23212 Option Delay between launch and boot complete doesnt work Was able to reproduce the described behavior using JNLP connection with a long post-boot delay and a short idle time to disconnect. The two features are colliding. Solutions: decrease post-boot delay to bare minimum needed, use non-JNLP slave agent connection, or increase the idle time to disconnect. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-23212) Option Delay between launch and boot complete doesn't work
Jason Swager resolved JENKINS-23212 as Not A Defect Option Delay between launch and boot complete doesnt work Expected behavior Change By: Jason Swager (30/Jun/14 3:27 AM) Status: Open Resolved Assignee: JasonSwager Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-23212) Option Delay between launch and boot complete doesn't work
Jason Swager commented on JENKINS-23212 Option Delay between launch and boot complete doesnt work This issue will be closed shortly. This appears to be expected behavior. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [parameterized-remote-trigger] (JENKINS-22325) Parameterized Remote Trigger Plugin fails with 'FATAL: Invalid JSON String' after triggering the remote build
Jason Swager commented on JENKINS-22325 Parameterized Remote Trigger Plugin fails with FATAL: Invalid JSON String after triggering the remote build I'm having this same problem. It looks like an update is supposed to be rolling out - but no trace of an update being available. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-23212) Option Delay between launch and boot complete doesn't work
Jason Swager commented on JENKINS-23212 Option Delay between launch and boot complete doesnt work I believe that this expected. Although Jenkins is starting the VM (power on), the VM is starting the slave agent on its own. It could be using the Windows Service, Task Scheduler or something else. Your config screen confirms that the slave agent is being started via JNLP. The log is showing that the JNLP is connecting (from the VM side) before the timeouts have ended on the Jenkins side. This is fine. The rapid disconnect is probably occurring due to the your idle disconnect timer. You have it set to 1 minute. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-21810) Additional options on slave disconnection
Jason Swager commented on JENKINS-21810 Additional options on slave disconnection Maybe you just need a "Hard Power Down"? If the slave is configured with a snapshot, that snapshot will be reverted to on slave startup as part of a normal startup. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-21810) Additional options on slave disconnection
Jason Swager commented on JENKINS-21810 Additional options on slave disconnection v1.1.19 and v1.1.20 both have the Revert and Reset/Restart, which should meet this feature request. This issue will be closed on June 1st if no further information is added. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-21466) Impossible to connect to the VSphere Cloud Anymore
Jason Swager commented on JENKINS-21466 Impossible to connect to the VSphere Cloud Anymore This is some VERY good information. I greatly appreciate the work that you did to hunt down the culprit of this problem. I'll check with the vijava project and see if a change can be pushed to them - or requested. Again, thanks for the help on getting to the root cause of this problem! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-21810) Additional options on slave disconnection
Jason Swager commented on JENKINS-21810 Additional options on slave disconnection Please try the latest v1.1.19 and try the Revert and Reset/Revert and Restart options. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-21647) In Vsphere Cloud I can not create a machine from a template
Jason Swager commented on JENKINS-21647 In Vsphere Cloud I can not create a machine from a template It's been discussed - just allowing a cluster to be assigned. The problem is that there are more error cases that could occur. So far, we haven't added code to handle that case. If you use the vSphere UIs to deploy, there's a number of validation checks applied during the selection process to ensure that you don't deploy to a wrong host that might be in a cluster. There's even logic that will force you to choose a host in the event that the cluster is not homogeneous. None of that logic would be duplicated in the vSphere plugin. That could allow for several failures to deploy for odd, cryptic, or just no good obvious reason. Classic example would be deploying a Mac VM to a cluster with UCS blades, or a UCS/Mac mix. By sticking to the resource, we're able to latch onto something definitive. It's still possible - just more error prone. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-21647) In Vsphere Cloud I can not create a machine from a template
Jason Swager commented on JENKINS-21647 In Vsphere Cloud I can not create a machine from a template Oh, very nice! A functioning workaround. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-22025) VM cannot be started repeatedly with vSphere plugin
Jason Swager resolved JENKINS-22025 as Fixed VM cannot be started repeatedly with vSphere plugin Increased power on timeout from 15 seconds to 1 minute. Change By: Jason Swager (13/Mar/14 10:34 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-21312) Vsphere plugin keeps reseting the slave when slave is configured for on demand start
Jason Swager resolved JENKINS-21312 as Fixed Vsphere plugin keeps reseting the slave when slave is configured for on demand start Increased power on timeout from 15 seconds to 1 minute. Also modified locking mechanism to use the VM rather than the Launcher. Change By: Jason Swager (13/Mar/14 10:35 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-22025) VM cannot be started repeatedly with vSphere plugin
Jason Swager commented on JENKINS-22025 VM cannot be started repeatedly with vSphere plugin The funny thing is that another user has a similar problem - but their start failure is for slaves, not the build steps. Same problem in both cases; host or vCenter under load or taking longer than expected to complete the operation. Solution is the same in both cases: increase the timeout. I hope to have a fix out for this in an official release in the next day or two. By the way, you don't need a full vCenter to perform the work - you can talk directly to ESXi. It has to be a license ESXi; not the free one you can get from VMware. The free one won't accept SDK commands that the vSphere Plugin uses. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-22025) VM cannot be started repeatedly with vSphere plugin
Jason Swager assigned JENKINS-22025 to Jason Swager VM cannot be started repeatedly with vSphere plugin Change By: Jason Swager (10/Mar/14 2:29 PM) Assignee: JasonSwager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-22025) VM cannot be started repeatedly with vSphere plugin
Jason Swager commented on JENKINS-22025 VM cannot be started repeatedly with vSphere plugin Sorry, there's no additional logging in this portion of the code. At the point where you are seeing the failure, the plugin is has sent a "Power On" command to the vCenter. That command queues up in vCenter and is processed. When the command is complete, it only means that the VM has been powered on, not that it is fully powered up and ready to go. You should be able to observe this behavior in vCenter if you power on a VM via one of the vSphere Clients (web or app). The Task name is "Power On virtual machine". Depending on how vCenter is configured, this command can execute very quickly, or more slowly, for example - if your vCenter is using DRS and the VM has to be migrated to another host before powering on. Anyway, the plugin has a 15 second delay, waiting for that task to complete. If the task doesn't complete in that amount of time, you get the error message that you did. In testing and in production, 15 seconds seems to have been adequate. But maybe it needs to be higher... If you could replicate the problem, then find the associated "Power On virtual machine" task in the vCenter task viewer, then find out the elapsed time between its Start Time and Completed Time. If the time is greater than 15 seconds, we know what the problem is - and how to solve it. If the time is much less than 15 seconds - we'll have to troubleshoot some more. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [vsphere-cloud] (JENKINS-21312) Vsphere plugin keeps reseting the slave when slave is configured for on demand start
Jason Swager commented on JENKINS-21312 Vsphere plugin keeps reseting the slave when slave is configured for on demand start I have a test version that MIGHT resolve this problem. Since I can't reproduce the problem exactly, I'm not sure if the changes will help your situation or not. If provided the HPI file, would you be able to test it? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21466) Impossible to connect to the VSphere Cloud Anymore
Jason Swager assigned JENKINS-21466 to Jason Swager Impossible to connect to the VSphere Cloud Anymore Change By: Jason Swager (03/Mar/14 5:00 AM) Assignee: JasonSwager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21312) Vsphere plugin keeps reseting the slave when slave is configured for on demand start
Jason Swager commented on JENKINS-21312 Vsphere plugin keeps reseting the slave when slave is configured for on demand start Sorry - I don't know of a way to change the polling time of Jenkins for cloud slaves. So far, I haven't been able to replicate your problem, even when I setup a slave that took 5 minutes to fully connect to Jenkins. I'm still trying to figure out what the problem really is. There is already code in the plugin to prevent multiple simultaneous power-ons for the same VM, but that doesn't seem to be working in your case. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21312) Vsphere plugin keeps reseting the slave when slave is configured for on demand start
Jason Swager commented on JENKINS-21312 Vsphere plugin keeps reseting the slave when slave is configured for on demand start Yes. The Revert operation is part of the connect sequence. The entire connect sequence is guarded to prevent multiple threads from starting the same slave. Likewise with the disconnect sequence. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21528) Can't turn on a VM
Jason Swager resolved JENKINS-21528 as Cannot Reproduce Cant turn on a VM Change By: Jason Swager (17/Feb/14 3:56 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21466) Impossible to connect to the VSphere Cloud Anymore
Jason Swager commented on JENKINS-21466 Impossible to connect to the VSphere Cloud Anymore Also, are you using vSphere 4.1 Update 1? Or the original vSphere 4.1? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21810) Additional options on slave disconnection
Jason Swager assigned JENKINS-21810 to Jason Swager Additional options on slave disconnection Change By: Jason Swager (17/Feb/14 4:12 AM) Assignee: JasonSwager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21528) Can't turn on a VM
Jason Swager commented on JENKINS-21528 Cant turn on a VM If there is no further feedback on this issue, it will closed. As noted, Jenkins doesn't allow a job running on a slave to terminate the slave connection; doing so is considered immediate job failure. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21528) Can't turn on a VM
Jason Swager assigned JENKINS-21528 to Jason Swager Cant turn on a VM Change By: Jason Swager (10/Feb/14 1:40 AM) Assignee: JasonSwager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21312) Vsphere plugin keeps reseting the slave when slave is configured for on demand start
Jason Swager commented on JENKINS-21312 Vsphere plugin keeps reseting the slave when slave is configured for on demand start So far, no luck in reproducing this problem. From the code of the plugin, it shouldn't be possible to power on a VM twice during the startup cycle. The only thing that I can guess at (and this doesn't look to be the case from your logs) is that two slaves - both point at the same VM are trying to start the slave. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21528) Can't turn on a VM
Jason Swager edited a comment on JENKINS-21528 Cant turn on a VM If there is no further feedback on this issue by Feb 16th, it will closed. As noted, Jenkins doesn't allow a job running on a slave to terminate the slave connection; doing so is considered immediate job failure. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21580) Server reverts to default value in vSphere Build Step when multiple vSphere Clouds exist
Jason Swager created JENKINS-21580 Server reverts to default value in vSphere Build Step when multiple vSphere Clouds exist Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: vsphere-cloud Created: 30/Jan/14 8:58 PM Description: This only happens when more than one vSphere Cloud is configured on the system. If a vSphere Build Step in a job is configured to use a cloud other than the first (default) one and the job is saved - the correct vSphere Cloud is saved with the job. Running the job will show that the correct vSphere Cloud was used. Configuring the job and going to the vSphere Build Step will show that the vSphere Cloud is now reset to the first (default) one. Saving the job will set this new Cloud. If you cancel from the configuration, the original Cloud value is still saved. Environment: Jenkins 1.549, vSphere Cloud 1.1.3 Project: Jenkins Priority: Critical Reporter: Jason Swager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21528) Can't turn on a VM
Jason Swager commented on JENKINS-21528 Cant turn on a VM If I understand this correctly, you're attempting to run a job on Slave "srv1". Slave "srv1" is VM "myserver". And the job is trying to turn on "myserver"? In other words, your job is attempting to power on the slave that it's running on? If that's your intent, that won't work. Jenkins only allows you to run jobs on slaves that are powered on and connected. You can't power on the slave that you're running the job on because Jenkins won't let you run the job on the slave UNTIL its powered on and connected. Thankfully, vSphere Cloud Slaves can handle this. If you setup the slave like you have (although I would recommend checking "Wait for VMTools" if you have them installed), then sending a job to that slave will automatically cause the slave to launch, if it's not already powered on. So there's no need for the power-on step in the job. If you intend to manipulate the slave VM as part of a Job (power on, power off, revert, clone), then you need to do it from a Job running elsewhere besides the slave. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21312) Vsphere plugin keeps reseting the slave when slave is configured for on demand start
Jason Swager commented on JENKINS-21312 Vsphere plugin keeps reseting the slave when slave is configured for on demand start Not certain how long this will take to resolve. I haven't been able to reproduce the problem on the test systems that I have, so I can't be certain if any code changes will fix your situation - or make it worse. There are a couple things that might help figure out what's going on though: 1) Is Wait for VMTools checked? And do you have VMTools installed on the VM? 2) What value are you using for "Delay between launch and boot complete"? 3) What "Secondary launch method" are you using. I know that it is possible to get the behavior you describe by NOT checking Wait for VMTool and having a "Delay between launch and boot complete" of 0. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21312) Vsphere plugin keeps reseting the slave when slave is configured for on demand start
Jason Swager commented on JENKINS-21312 Vsphere plugin keeps reseting the slave when slave is configured for on demand start Uh oh. Based on this log, it does indeed look like Jenkins is constantly trying to restart the VM. Let me investigate further. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21312) Vsphere plugin keeps reseting the slave when slave is configured for on demand start
Jason Swager assigned JENKINS-21312 to Jason Swager Vsphere plugin keeps reseting the slave when slave is configured for on demand start Change By: Jason Swager (09/Jan/14 5:22 PM) Assignee: JasonSwager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21312) Vsphere plugin keeps reseting the slave when slave is configured for on demand start
Jason Swager commented on JENKINS-21312 Vsphere plugin keeps reseting the slave when slave is configured for on demand start According to this log, Jenkins is trying to launch TWO different slaves: Vistax86_sp2 and Vistax64_sp1. The log shows that Jenkins was starting those two slaves. Are those slaves the SAME VM (ie, different snapshots, or perhaps just misconfiguration) or DIFFERENT VMs? From this log, I don't see any attempt to reset the same slave. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-20035) see exclusively and possible assigned jobs (by tags) in node view
Jason Swager updated JENKINS-20035 see exclusively and possible assigned jobs (by tags) in node view Removing vmware and vsphere cloud tags; adding core. This is a core issue and cannot be addressed in this plugin. Change By: Jason Swager (18/Nov/13 5:06 AM) Component/s: core Component/s: vmware Component/s: vsphere-cloud This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-20011) new slave schedule typ: only power on machine if job requests it
Jason Swager updated JENKINS-20011 new slave schedule typ: only power on machine if job requests it Removing vSphere Cloud tag, adding core so that Core folks can take a look at. Also removing assignment to me. The problem appears to be that for some reason, Jenkins is wanting to run something on their VM slave. No jobs appear in the history, but it gets started up. Since the vSphere Cloud slave is just responding to a Jenkins request to Connect(), the question is why is Jenkins requesting a connect. Not a vSphere Plugin problems that I'm aware of. Change By: Jason Swager (12/Nov/13 11:17 PM) Assignee: JasonSwager Component/s: core Component/s: vsphere-cloud This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [slave-setup] (JENKINS-20011) only try to poer on machine if job requests ist
Jason Swager commented on JENKINS-20011 only try to poer on machine if job requests ist The feature will have to come from the Jenkins core. Jenkins says Connect() - that's what the slave does, whatever it takes. And Jenkins will follow those three schedules. There is an existing Jenkins feature: Temporary Offline. If you click on a slave, you can select "Mark this node temporarily offline". When you do that, you can then do whatever you want with the slave VM and Jenkins won't turn it on, or off, or run jobs on it. When I perform maintenance on our slaves, that's the method that I use: put the slave in temporarily offline, then do the maintenance, then bring it back online. But it does take some degree of access. That would the last thing to offer. To have Jenkins and the slaves work EXACTLY like you describe, you would have to go into Jenkins core and add new type of scheduling. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [slave-status] (JENKINS-19445) Jobs randomly stuck with building remotely on slave-name message
Jason Swager commented on JENKINS-19445 Jobs randomly stuck with building remotely on slave-name message Winstone as well This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [vmware] (JENKINS-20011) only try to poer on machine if job requests ist
Jason Swager commented on JENKINS-20011 only try to poer on machine if job requests ist Just to confirm - you don't want Jenkins to power the slave on or off, just use the slave if it is online? If this is what you want, then using the vSphere Cloud slave is NOT what you should do. You want to use the Jenkins Dumb Slave - even though the slave is a VM. The Dumb Slave has no capability to turn on or off - it relies on something other than Jenkins (human, timer based power strips, BIOS power timer controls, whatever) to turn the slave on off. If Jenkins sends a job to slave like that, it will just remain in the queue until the slave is powered on and connected. Have you tried just using the Dumb Slave? Recommend giving that a try and seeing how that work for your situation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [vmware] (JENKINS-20011) only try to poer on machine if job requests ist
Jason Swager commented on JENKINS-20011 only try to poer on machine if job requests ist If you don't want Jenkins to control the slave as if it where a VM - allowing power-on, power-off, revert on demand - then I would suggest that you don't need the slave to be a vSphere Cloud slave, but just a normal dumb slave. Jenkins lets you create those and leaves the turning on, turning off to you. The intent behind the vSphere Cloud slaves is that Jenkins can control the slave more closely. It sounds like you don't want it to have that degree of control. The dumb slave would probably work better for you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-17095) Vsphere cloud plugin won't revert to a snapshot
Jason Swager commented on JENKINS-17095 Vsphere cloud plugin wont revert to a snapshot I've been trying to reproduce this issue on a couple different vCenters - but no luck so far. If there was a build step for this plugin to perform the revert, it still wouldn't work. The problem is not so much in the plugin - as in the communication with vCenter. vCenter just won't do the revert when asked to. If the API call was in question, then it would fail on all systems. Looking back through the notes, I did see something interesting: INFO: vsphere Got an exception Mar 6, 2013 10:19:50 AM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: vsphere com.vmware.vim25.RestrictedVersion The RestrictedVersion has me wondering if the vCenter is somehow restricting the API from performing a revert. I KNOW that vCenter is sensative to how it gets it commands. The vSphere Client may be able to perform certain actions, but those same actions - performed via any API (PowerShell, Java, Python, whatever) will be rejected due to the licensing of vCenter. Classic example is the free ESXi host. Can't control it via API, only via the vSphere Client. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-16960) Status Code: 500/ NullPointerException when running command in slave script console
Jason Swager assigned JENKINS-16960 to Jason Swager Status Code: 500/ NullPointerException when running command in slave script console Change By: Jason Swager (28/Mar/13 3:51 PM) Assignee: JasonSwager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-16960) Status Code: 500/ NullPointerException when running command in slave script console
Jason Swager commented on JENKINS-16960 Status Code: 500/ NullPointerException when running command in slave script console What command did you enter into the Script Console? I tried a couple simple ones and there were no errors - got expected response. Also, what sort of slave are you running the commands on? And was the slave connected at the time you ran the command? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-16590) Wrong Load Statistics Graph
Jason Swager commented on JENKINS-16590 Wrong Load Statistics Graph Is this problem still happening with Jenkins 1.508? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-15504) NPE on running a job
Jason Swager assigned JENKINS-15504 to Jason Swager NPE on running a job Change By: Jason Swager (28/Mar/13 3:59 PM) Assignee: JasonSwager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-17323) Log lines print without newlines
Jason Swager assigned JENKINS-17323 to Jason Swager Log lines print without newlines Change By: Jason Swager (28/Mar/13 3:59 PM) Assignee: JasonSwager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-17341) Promoted builds throw NullPointerException after upgrade to 1.507
Jason Swager updated JENKINS-17341 Promoted builds throw NullPointerException after upgrade to 1.507 Change By: Jason Swager (25/Mar/13 8:07 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-17341) Promoted builds throw NullPointerException after upgrade to 1.507
Jason Swager commented on JENKINS-17341 Promoted builds throw NullPointerException after upgrade to 1.507 Also experiencing the same problem: Jenkins 1.507 and Promoted plugin 2.8. Using Win2008R2 Server though. Raised issue to Critical priority. Any jobs that use the plugin will be appear to have been deleted from Jenkins. Reverting Jenkins resolved the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-15560) Lazy loading cause’s http links from other html pages into Jenkins do not work properly
Jason Swager commented on JENKINS-15560 Lazy loading cause’s http links from other html pages into Jenkins do not work properly 404 error code is the result. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-17095) Vsphere cloud plugin won't revert to a snapshot
Jason Swager commented on JENKINS-17095 Vsphere cloud plugin wont revert to a snapshot I'm guessing that you're connecting directly to the vCenter itself, and not to the ESXi host? I'm a little at loss for this issue. From what I can tell, VMware - the server side, not the client side - is disconnecting for some reason. I'm not sure that this can even be fixed from a client side perspective. It feels more like server side configuration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-17095) Vsphere cloud plugin won't revert to a snapshot
Jason Swager commented on JENKINS-17095 Vsphere cloud plugin wont revert to a snapshot Are you using a licensed version of ESX 4.1.0 with a vCenter? Or are you using the free, stand-alone ESXi offered by VMware? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-17095) Vsphere cloud plugin won't revert to a snapshot
Jason Swager assigned JENKINS-17095 to Jason Swager Vsphere cloud plugin wont revert to a snapshot Change By: Jason Swager (06/Mar/13 2:53 PM) Assignee: JasonSwager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-16932) Exception: net.sf.json.JSONException: JSONObject[tag] not found when doing a rebuild
Jason Swager commented on JENKINS-16932 Exception: net.sf.json.JSONException: JSONObject[tag] not found when doing a rebuild Full Stack Trace: javax.servlet.ServletException: net.sf.json.JSONException: JSONObjecttag not found. at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at
[JIRA] (JENKINS-16932) Exception: net.sf.json.JSONException: JSONObject[tag] not found when doing a rebuild
Jason Swager created JENKINS-16932 Exception: net.sf.json.JSONException: JSONObject[tag] not found when doing a rebuild Issue Type: Bug Affects Versions: current Assignee: ragesh_nair Components: rebuild Created: 22/Feb/13 3:44 PM Description: When attempting to do a rebuild of a set of jobs, the following error is encountered: Exception: net.sf.json.JSONException: JSONObjecttag not found. Not all of our jobs generate this error, which makes me think it is a particular plugin/parameter that has the problem. The job uses normal text string, the NodeLabel parameter (to dictate the slave), multiple Build Selector for Copy Artifact parameters. Environment: Jenkins 1.501, Rebuild 1.17 Project: Jenkins Priority: Major Reporter: Jason Swager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-16590) Wrong Load Statistics Graph
Jason Swager assigned JENKINS-16590 to Jason Swager Wrong Load Statistics Graph Change By: Jason Swager (08/Feb/13 2:18 AM) Assignee: JasonSwager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-16590) Wrong Load Statistics Graph
Jason Swager commented on JENKINS-16590 Wrong Load Statistics Graph The vSphere plugin doesn't do anything with executor counts or metrics. That's all handled by the base slave class. Are these metrics the same if the slave is not a vSphere slave, but just a normal dumb slave that is connected and disconnected multiple times? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-16590) Wrong Load Statistics Graph
Jason Swager commented on JENKINS-16590 Wrong Load Statistics Graph That's a nice looking graph. Is that of a slave that is taking jobs over a period of time? Could you obtain a graph where the slave is disconnected (powered down, slave agent terminated) for a period of time, then restored. Essentially, that's what a vSphere slave is doing - turning on to run a job, then shutting down, starting up again, etc. I'm wondering if that behavior (not always present slave) is the cause of this odd graph. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-16535) vSphereCloud plugin doesn't work with vSphere 5.1
Jason Swager resolved JENKINS-16535 as Not A Defect vSphereCloud plugin doesnt work with vSphere 5.1 Problem was in understanding how the options work rather than an actual defect. Change By: Jason Swager (01/Feb/13 2:33 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-16535) vSphereCloud plugin doesn't work with vSphere 5.1
Jason Swager commented on JENKINS-16535 vSphereCloud plugin doesnt work with vSphere 5.1 I have no idea what the sCCL log lines are for. They're not from the vSphere Cloud Plugin, but maybe from another plugin. The vSphere Cloud Plugin can start the VM (as you found), but getting the slave agent running can be a bit more tricky. 1) The Windows Service was unreliably in our environment, most likely due to our locked down machines and some bizarre parts of our network topography. Others have had used it to good effect. So your usage may vary. 2) The SSH approach will work. Windows doesn't have a native SSH server, but you can add them. I found that the Windows SSH servers don't always work perfect with the default Jenkins SSH slave starting, although it was possible to craft custom SSH commands that would work with the server. Although it can work, we don't use that approach because we have no static IP addresses in our environment, everything is DHCP driven. 3) My preferred method is the Java Web Start. It require a bit more manual work on the slave, but it works in our environment robustly. Simply put, all you have to do is have Java installed on the slave and somewhere, somehow, add a command to the slaves startup sequence. The command is simply "javaws http://YourJenkins/computer/SlaveName/slave-agent.jnlp" For Windows machines, I can put that in a CMD file that runs from the Startup Folder of a machine with AutoLogin enabled. Or a Scheduled Task. For Mac, a Startup Item that's an Automation Script. For Linux, a Login Item that runs a bash script that contains this command. Which ever way works for you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-16535) vSphereCloud plugin doesn't work with vSphere 5.1
Jason Swager assigned JENKINS-16535 to Jason Swager vSphereCloud plugin doesnt work with vSphere 5.1 Change By: Jason Swager (30/Jan/13 4:30 PM) Assignee: JasonSwager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-16535) vSphereCloud plugin doesn't work with vSphere 5.1
Jason Swager commented on JENKINS-16535 vSphereCloud plugin doesnt work with vSphere 5.1 Can you give me more details of the problem? We've been using the plugin with vSphere 5.1 for over a month now without problem. According to the files you sent, it appears that you're not letting Jenkins start the VM, but waiting for someone else to start it. Try checking "Force VM Launch" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-15594) CopyArtifact plugin cannot always copy artifacts
Jason Swager commented on JENKINS-15594 CopyArtifact plugin cannot always copy artifacts I don't think this is a case of permissions. I think this is a case of the job/build lazy-load not yet loading the build in question. Similar issues have been happening with Build URLs. You can paste the URL of a build into a browser and Jenkins responds with a 404. But if you go into Jenkins, locate the job, then drill down to the build, it always works. Then pasting the URL will work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16104) Build Failure Analyzer: Ugly output from plugin
Jason Swager commented on JENKINS-16104 Build Failure Analyzer: Ugly output from plugin Also experiencing this problem. Finding that it occurs in a couple situations: 1) If the build if failed due to a timeout (Timeout plugin), this reliably seems to appear. 2) An exception is generated in the Email-Ext plugin, this will often appear. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15560) Lazy loading cause’s http links from other html pages into Jenkins do not work properly
Jason Swager commented on JENKINS-15560 Lazy loading cause’s http links from other html pages into Jenkins do not work properly I'm not sure of any easy way to reproduce. A temporary solution seems to be rebooting Jenkins. The way that I would try to reproduce is to load Jenkins with lots of jobs and lots of builds for each job. I'm guessing that if the memory used by the job/build objects is very high in regards to the available memory (sorry - don't know how to define "high"), the problem might occur. Having the jobs limit their number of archived builds, then running many times beyond that so that archived builds are being deleted might help cause the problem; I'm guessing this because a reboot temporarily fixes our problem. And although we keep 20 to 50 builds archived on each job, we have a high enough turn over that in two weeks, all builds are replaced - and the problem seems to happen the longer we run... Sorry for the vague and imprecise descriptions. When the problem occurs, we usually go into panic mode because Jenkins begins to fail in a variety of ways and we don't have a lot of time before we get flooded with calls from managers/engineers complaining about false build/test failure notifications, busted dashboards, etc. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15560) Lazy loading cause’s http links from other html pages into Jenkins do not work properly
Jason Swager commented on JENKINS-15560 Lazy loading cause’s http links from other html pages into Jenkins do not work properly Our Jenkins installation (1.496, Win2008R2) is having the same problems. A month ago, it was sporadic - once every 1000 builds or so. But we just finished adding a couple hundred more jobs and the problem got immediately worse. It's not just URLs to builds that is affected - other components also break for the same reason I suspect. The Copy Artifact plugin seems to have a similar problem. It will cause a build failure because it can't download artifacts from a specific build. This will happen repeatedly until someone uses a browser, goes to the job and specifically loads the problematic build. Once the build is display, the job can be run successfully. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15560) Lazy loading cause’s http links from other html pages into Jenkins do not work properly
Jason Swager updated JENKINS-15560 Lazy loading cause’s http links from other html pages into Jenkins do not work properly Due to the nature of this bug, I'm bumping the issue up to Critical. It affects not only core Jenkins functionality, but also the behavior of some plugins. Change By: Jason Swager (03/Jan/13 9:36 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15236) Add an option to not fail a job if workspace deletion fails
Jason Swager commented on JENKINS-15236 Add an option to not fail a job if workspace deletion fails We have the same problem. For us, it's a big blocker. Because the job fails due to workspace cleanup, the next part of the build/test chains won't execute because the job has a status of failed. Ideally, it would be best to fix the exception so that it doesn't happen and the builds never fail. But if there's no way to fix the exception, then a way to keep the build from being marked as failed would be the next best thing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13939) Workspace cleanup plugin causes Jenkins to consider a job as completed before it is actually done
Jason Swager commented on JENKINS-13939 Workspace cleanup plugin causes Jenkins to consider a job as completed before it is actually done Could this be related to JENKINS-15236? Perhaps the failures in workspace cleanups is because another job (or another build of the same job) started running in the same workspace before the current job had a chance to cleanup? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15236) Add an option to not fail a job if workspace deletion fails
Jason Swager commented on JENKINS-15236 Add an option to not fail a job if workspace deletion fails I can understand exceptions on locked files. Actually, if there locked files at the end of a build, I want to know about it because I would consider that a failure. But in cases where I'm certain there are no locked files, I would expect no exceptions and no failure due to inability to cleanup. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
