[JIRA] (JENKINS-58109) Perforce ditto mappings from clientspec do not work
Title: Message Title
Jason Davis commented on JENKINS-58109
Re: Perforce ditto mappings from clientspec do not work
FWIW - I have a ditto path that I use in a script block in a declarative pipeline. It looks like this:
script {
PerforceViewMap = """//Path1/... //jenkins-${JOB_BASE_NAME}-${NODE_NAME}/Path1/...
//DittoPath1/... //jenkins-${JOB_BASE_NAME}-${NODE_NAME}/Path1/DittoPathA/...
//Path2/... //jenkins-${JOB_BASE_NAME}-${NODE_NAME}/Path2/...
&//DittoPath1/... //jenkins-${JOB_BASE_NAME}-${NODE_NAME}/Path2/DittoPathB/...
//Path3/... //jenkins-${JOB_BASE_NAME}-${NODE_NAME}/Path3/..."""
PerforceSource = perforce(browser: swarm('http://swarm.myserver.com'),
credential: 'creds',
populate: forceClean(have: true, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'],
pin: '', quiet: true),
workspace: manualSpec(charset: 'none',
name: 'jenkins-${JOB_BASE_NAME}-${NODE_NAME}', pinHost: false,
spec: clientSpec(allwrite: true, backup: false, clobber: true, compress: false,
line: 'LOCAL', locked: false, modtime: false, rmdir: true, serverID: '', streamName: '', type: 'WRITABLE',
view: PerforceViewMap)))
}
checkout scm: PerforceSource
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-56317) Download from File Shares Seems to Not Use Ant Syntax
Title: Message Title
Jason Davis created an issue
Jenkins / JENKINS-56317
Download from File Shares Seems to Not Use Ant Syntax
Issue Type:
Bug
Assignee:
Azure DevOps
Attachments:
steps-doc.png
Components:
windows-azure-storage-plugin
Created:
2019-02-27 20:05
Environment:
Plugin: 0.3.13 Jenkins Version: 2.150.3
Priority:
Minor
Reporter:
Jason Davis
Not sure if this is a bug, but the docs might be confusing me. I'm trying a simple test to see if I can download specific files directly from a specific location in a storage account. I created a storage account and manually uploaded a foo.txt file to an "artifacts" File Share under a subfolder called Secrets. I uploaded a copy off another in a different subfolder (Azure-Storage-Upload) of the same File Share The pipeline syntax step suggests that downloading from the File Share is possible and that files can be downloaded using ant fileset syntax (I attached a screenshot of the syntax help) I created a simple pipeline:
pipeline{
agent any
stages{
stage ('Do Something'){
steps{
echo 'download'
azureDownload downloadType: 'share',
fileShare: 'artifacts',
includeFilesPattern: 'Secrets/foo.txt',
storageCredentialId: 'jenkins-devops-test-02'
}
}
}
}
[JIRA] (JENKINS-56251) Plugin Finds Files Only in Master Workspaces?
Title: Message Title
Jason Davis created an issue
Jenkins / JENKINS-56251
Plugin Finds Files Only in Master Workspaces?
Issue Type:
Bug
Assignee:
mo xun
Components:
content-replace-plugin
Created:
2019-02-22 16:52
Environment:
Jenkins (Windows) - versions 2.138.3 and 2.150.3 Content Replace Plugin 1.0.4 Nodes = Win2016
Priority:
Minor
Reporter:
Jason Davis
The script below works to find and update a file if the file exists in the workspace on the Jenkins master. When updating the label to run on a node, and ensuring the file does in fact exist in the workspace of the node, the script fails stating that that the file does not exist. In case it matters, the jobs are managed in a Jenkins folder. java.io.FileNotFoundException: File 'C:\jenkins\workspace\Pipeline-Tests\Content-Replace-Test\here.txt' does not exist at org.apache.commons.io.FileUtils.openInputStream(FileUtils.java:299) at org.apache.commons.io.FileUtils.readFileToString(FileUtils.java:1711) Pipeline with
pipeline{
agent none
stages {
stage ("Do Stuff") {
agent { label 'master' }
stages {
stage ("Test") {
steps {
echo 'Replace...'
contentReplace(configs: [fileContentReplaceConfig(configs:
[fileContentReplaceItemConfig(matchCount: 1,
replace: "versionName-replace",
search: 'versionName.*')],
fileEncoding: 'ASCII',
[JIRA] (JENKINS-56251) Plugin Finds Files Only in Master Workspaces?
Title: Message Title
Jason Davis updated an issue
Jenkins / JENKINS-56251
Plugin Finds Files Only in Master Workspaces?
Change By:
Jason Davis
The script below works to find and update a file if the file exists in the workspace on the Jenkins master. When updating the label to run on a node, and ensuring the file does in fact exist in the workspace of the node, the script fails stating that that the file does not exist. In case it matters, the jobs are managed in a Jenkins folder. {code: java }java .io.FileNotFoundException: File 'C:\jenkins\workspace\Pipeline-Tests\Content-Replace-Test\here.txt' does not exist at org.apache.commons.io.FileUtils.openInputStream(FileUtils.java:299) at org.apache.commons.io.FileUtils.readFileToString(FileUtils.java:1711) {code} Pipeline with Sequential Steps {code:java}pipeline{agent nonestages {stage ("Do Stuff") {agent { label 'master' } stages {stage ("Test") {steps { echo 'Replace...' contentReplace(configs: [fileContentReplaceConfig(configs: [fileContentReplaceItemConfig(matchCount: 1, replace: "versionName-replace", search: 'versionName.*')], fileEncoding: 'ASCII', filePath: 'here.txt')])}}}}}}{code}
Add Comment
This message was
[JIRA] (JENKINS-56251) Plugin Finds Files Only in Master Workspaces?
Title: Message Title
Jason Davis created an issue
Jenkins / JENKINS-56251
Plugin Finds Files Only in Master Workspaces?
Issue Type:
Bug
Assignee:
mo xun
Components:
content-replace-plugin
Created:
2019-02-22 16:52
Environment:
Jenkins (Windows) - versions 2.138.3 and 2.150.3 Content Replace Plugin 1.0.4 Nodes = Win2016
Priority:
Minor
Reporter:
Jason Davis
The script below works to find and update a file if the file exists in the workspace on the Jenkins master. When updating the label to run on a node, and ensuring the file does in fact exist in the workspace of the node, the script fails stating that that the file does not exist. In case it matters, the jobs are managed in a Jenkins folder. java.io.FileNotFoundException: File 'C:\jenkins\workspace\Pipeline-Tests\Content-Replace-Test\here.txt' does not exist at org.apache.commons.io.FileUtils.openInputStream(FileUtils.java:299) at org.apache.commons.io.FileUtils.readFileToString(FileUtils.java:1711) Pipeline with
pipeline{
agent none
stages {
stage ("Do Stuff") {
agent { label 'master' }
stages {
stage ("Test") {
steps {
echo 'Replace...'
contentReplace(configs: [fileContentReplaceConfig(configs:
[fileContentReplaceItemConfig(matchCount: 1,
replace: "versionName-replace",
search: 'versionName.*')],
fileEncoding: 'ASCII',
[JIRA] (JENKINS-56251) Plugin Finds Files Only in Master Workspaces?
Title: Message Title
Jason Davis updated an issue
Jenkins / JENKINS-56251
Plugin Finds Files Only in Master Workspaces?
Change By:
Jason Davis
The script below works to find and update a file if the file exists in the workspace on the Jenkins master. When updating the label to run on a node, and ensuring the file does in fact exist in the workspace of the node, the script fails stating that that the file does not exist. In case it matters, the jobs are managed in a Jenkins folder. {code: java }java .io.FileNotFoundException: File 'C:\jenkins\workspace\Pipeline-Tests\Content-Replace-Test\here.txt' does not exist at org.apache.commons.io.FileUtils.openInputStream(FileUtils.java:299) at org.apache.commons.io.FileUtils.readFileToString(FileUtils.java:1711) {code} Pipeline with Sequential Steps {code:java}pipeline{agent nonestages {stage ("Do Stuff") {agent { label 'master' } stages {stage ("Test") {steps { echo 'Replace...' contentReplace(configs: [fileContentReplaceConfig(configs: [fileContentReplaceItemConfig(matchCount: 1, replace: "versionName-replace", search: 'versionName.*')], fileEncoding: 'ASCII', filePath: 'here.txt')])}}}}}}{code}
Add Comment
This message was
[JIRA] (JENKINS-46722) alwaysLinkToLastBuild not linking to last job result
Title: Message Title Jason Davis commented on JENKINS-46722 Re: alwaysLinkToLastBuild not linking to last job result Also seeing this issue. Workarounds appreciated! 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-51902) build-timestamp-plugin does not ignore empty 3rd field 'shift timestamp'
Title: Message Title Jason Davis commented on JENKINS-51902 Re: build-timestamp-plugin does not ignore empty 3rd field 'shift timestamp' Matthew Hall - Thanks for the hack/workaround. I also lost my preconfigured additional timestamps after upgrading the plugin to the latest. Couldn't recreate them until I found this. 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-42753) Using a Pipeline Property with an Agent Label?
Title: Message Title Jason Davis commented on JENKINS-42753 Re: Using a Pipeline Property with an Agent Label? Bummer... OK - before reaching out with this issue, I did try both those recommendations but ran into troubles before I had to roll back the plugin updates. I'm not at a place yet where I can re-set up some tests and report the results, but will asap. Hopefully you hit on solution. 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-42753) Using a Pipeline Property with an Agent Label?
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-42753 Using a Pipeline Property with an Agent Label? Change By: Jason Davis Summary: Using a Pipeline Property with an Agent Label? 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-42753) Using a Pipeline Property an Agent Label?
Title: Message Title
Jason Davis updated an issue
Jenkins / JENKINS-42753
Using a Pipeline Property an Agent Label?
Change By:
Jason Davis
My apologies if this isn't a bug, but I've searched high and low and tried a number of things, but I can't seem to find the syntax ex. to solve what's broken. After upgrading pipeline plugins to the latest releases (as of today), my declarative pipelines broke because it seems there might no longer be ability to use a property in the agent label. I had something like this This was working :{noformat}pipeline{parameters {choice(choices: 'server-cd\server-demo', description: DeployEnvironmentHelp, name: 'Environment')} environment {DEPLOYENVIRONMENT = "${params.Environment}"}agent nonestages {stage ("Stage 1") {agent {label DEPLOYENVIRONMENT}echo 'Get Deployment Helper Files from SCM repo(s)...'}} }{noformat}But the pipeline fails saying that the DEPLOYENVIRONMENT is not a proper value (I no longer have the exact message :() As of model def. 1.1.1, is it no longer possible to use an environment variable or property in the agent label? btw - I'm setting DEPLOYENVIRONMENT so I can do other tests and not have to keep using params.Environment, but in other pipelines I set properties so that I can define which agent based on properties that change in the pipeline.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42753) Using a Pipeline Property an Agent Label?
Title: Message Title
Jason Davis commented on JENKINS-42753
Re: Using a Pipeline Property an Agent Label?
Whoops sorry for not making that more clear! Yes, agent {label DEPLOYENVIRONMENT} was working and is no longer.
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-42753) Using a Pipeline Property an Agent Label?
Title: Message Title
Jason Davis created an issue
Jenkins / JENKINS-42753
Using a Pipeline Property an Agent Label?
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2017/Mar/14 1:59 PM
Priority:
Minor
Reporter:
Jason Davis
My apologies if this isn't a bug, but I've searched high and low and tried a number of things, but I can't seem to find the syntax ex. to solve what's broken. After upgrading pipeline plugins to the latest releases (as of today), my declarative pipelines broke because it seems there might no longer be ability to use a property in the agent label. I had something like this:
pipeline{
parameters {
choice(choices: 'server-cd\server-demo', description: DeployEnvironmentHelp, name: 'Environment')
}
environment {
DEPLOYENVIRONMENT = "${params.Environment}"
}
agent none
stages {
stage ("Stage 1") {
agent {label DEPLOYENVIRONMENT}
echo 'Get Deployment Helper Files from SCM repo(s)...'
}
}
}
But the pipeline fails saying that the DEPLOYENVIRONMENT is not a proper value (I no longer have the exact message ) As of model def. 1.1.1, is it no longer possible to use an environment variable or property in the agent label? btw - I'm setting DEPLOYENVIRONMENT so I can do other tests and not have to keep using params.Environment, but in other pipelines I set properties so that I can define which agent based on properties that change in the pipeline.
[JIRA] (JENKINS-41118) Allow custom workspaces in declarative pipeline
Title: Message Title Jason Davis commented on JENKINS-41118 Re: Allow custom workspaces in declarative pipeline Without surveying, who knows, but for me it hits about 5-10% of builds. Another mentioned the same above - so I would think that it must be a reasonable requirement. My experience, wherever I work, it seems there's some legacy Windows build that is not going to get re-architected and has a really long path where only a custom workspace will help get the path short enough to compile. Without some way to control the workspace, there's no way to pipeline for those jobs and so I'm stuck with Freestyle, which poses other "how-to" problems like MultiSCM plugin bugs not being fixed due to pipelines. On a side note, reconciling both pipelining methods and providing a standard Jenkins "way" to do this would be even more useful moving forward, but that's clearly a different story... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41335) Allow variables and functions to be defined within pipeline to be used in any stage
Title: Message Title
Jason Davis commented on JENKINS-41335
Re: Allow variables and functions to be defined within pipeline to be used in any stage
I agree with Liam Newman (I think ). My two cents, Declarative pipelining makes a ton of sense and it feels like a more natural model than Scripted pipelining. In declarative land, though, to get the job done, I still end up needing if-then logic, to assign variables (as per this JIRA issue), using shared functions in groovy scripts – all those things need to be wrapped with script {. Really unifying the two methods back into one official "way" to pipeline, would be great for pipeline development. It'll reduce the maintenance burden on Jenkins jobs down the road too.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41706) "Override Git Credentials" Value Ignored During Release
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-41706 "Override Git Credentials" Value Ignored During Release Change By: Jason Davis When performing a release to Artifactory with Bitbucket source - I noticed on Linux that I had to add a username and email with permissions to the repository. Don't know if this is the Artifactory plugin's or git client plugin's fault, but I didn't have to do this when releasing the same project on Windows. The error and solution I found are here:http://stackoverflow.com/questions/41288988/jenkins-artifactory-release-plugin-unable-to-commit-tag-windows-host-machineThe problem that appears to be related the Artifactory plugin is that after adding this global config, the "Override Git credentials" option that's available in the Artifactory Release Staging screen when performing a release appears to be being ignored at the end of the release process when updated poms are given their new release and snapshot versions and checked back into the repository.We provided specific user credentials with write permissions to our Bitbucket repository (say User A), but the user that ended up checking in the updated poms for the release was the user we had to configure in the Global System Config area (Say User B). This is undesirable since User A actually works on the project and is performing the release, while User B, is a Bitbucket Admin, but isn't associated with any real work on the project. In the screenshots below, it shows Jason performed the commit back to bitbucket during the release, but the user that actually peformed the release was different and had provided his credentials in the Override Git credentials section. If we don't provide a global config, then the plugin fails to commit the final changed poms back to the repository as per the stackoverflow url proided above. Add Comment
[JIRA] (JENKINS-41706) "Override Git Credentials" Value Ignored During Release
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-41706 "Override Git Credentials" Value Ignored During Release Change By: Jason Davis Attachment: globaluser_didthecommit.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41706) "Override Git Credentials" Value Ignored During Release
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-41706 "Override Git Credentials" Value Ignored During Release Change By: Jason Davis Attachment: global_config.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41706) "Override Git Credentials" Value Ignored During Release
Title: Message Title Jason Davis created an issue Jenkins / JENKINS-41706 "Override Git Credentials" Value Ignored During Release Issue Type: Bug Assignee: Eyal Ben Moshe Attachments: global_config.png Components: artifactory-plugin Created: 2017/Feb/03 2:12 PM Environment: git client 2.10 - linux Build agent performing the release - linux centos 6.8 jenkins 2.31 - windows 2008 R2 artifactory plugin 2.90 bitbucket.org repository Priority: Major Reporter: Jason Davis When performing a release to Artifactory with Bitbucket source - I noticed on Linux that I had to add a username and email with permissions to the repository. Don't know if this is the Artifactory plugin's or git client plugin's fault, but I didn't have to do this when releasing the same project on Windows. The error and solution I found are here: http://stackoverflow.com/questions/41288988/jenkins-artifactory-release-plugin-unable-to-commit-tag-windows-host-machine The problem that appears to be related the Artifactory plugin is that after adding this global config, the "Override Git credentials" option that's available in the Artifactory Release Staging screen when performing a release appears to be being ignored at the end of the release process when updated poms are given their new release and snapshot versions and checked back into the repository. We provided specific user credentials with write permissions to our Bitbucket repository (say User A), but the user that ended up checking in the updated poms for the release was the user we had to configure in the Global System Config area (Say
[JIRA] (JENKINS-41623) Variable Expansion in Global Variables Not Occurring
Title: Message Title
Jason Davis updated an issue
Jenkins / JENKINS-41623
Variable Expansion in Global Variables Not Occurring
Change By:
Jason Davis
For Not sure about standard Pipeline scripts, but in a Declarative Pipeline script, for a given global variable built via:Jenkins -> Manage Jenkins -> Configure System{code}Name: MYPATH Value: ${WORKSPACE}/../path1/${JOB_BASE_NAME}{code}{code}...stage ("stage left") {steps {echo "MYPATH is: " + MYPATH...{code}The output in the script is:{code}[Pipeline] echoMYPATH is: ${WORKSPACE}/../path1/${JOB_BASE_NAME}{code}In Freestyle scripts the WORKSPACE and JOB_BASE_NAME values are expanded at build time. We use these as a nice way to have a few consistent job behaviors across all jobs, but without variable expansion, it seems we have to build and maintain variables in each job script.
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
[JIRA] (JENKINS-41623) Variable Expansion in Global Variables Not Occurring
Title: Message Title
Jason Davis created an issue
Jenkins / JENKINS-41623
Variable Expansion in Global Variables Not Occurring
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2017/Feb/01 1:08 PM
Environment:
Jenkins 2.32.1 Definition Plugin 0.9.1
Priority:
Minor
Reporter:
Jason Davis
For a given global variable built via: Jenkins -> Manage Jenkins -> Configure System
Name: MYPATH
Value: ${WORKSPACE}/../path1/${JOB_BASE_NAME}
...
stage ("stage left") {
steps {
echo "MYPATH is: " + MYPATH
...
The output in the script is:
[Pipeline] echo
MYPATH is: ${WORKSPACE}/../path1/${JOB_BASE_NAME}
In Freestyle scripts the WORKSPACE and JOB_BASE_NAME values are expanded at build time. We use these as a nice way to have a few consistent job behaviors across all jobs, but without variable expansion, it seems we have to build
[JIRA] (JENKINS-32368) Changes list is not showing the correct changes in a build
Title: Message Title Jason Davis closed an issue as Fixed This is issue no longer exists. Fixed in one of the last few releases of the plugin. Jenkins / JENKINS-32368 Changes list is not showing the correct changes in a build Change By: Jason Davis Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-41428) Tool Location Configuration Removed when Configuring System
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-41428 Tool Location Configuration Removed when Configuring System Change By: Jason Davis Attachment: Template Tool Configuration Saved.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41428) Tool Location Configuration Removed when Configuring System
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-41428 Tool Location Configuration Removed when Configuring System Change By: Jason Davis Attachment: After Re-editing Jenkins System Config.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41428) Tool Location Configuration Removed when Configuring System
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-41428 Tool Location Configuration Removed when Configuring System Change By: Jason Davis Attachment: tool-saved.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41428) Tool Location Configuration Removed when Configuring System
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-41428 Tool Location Configuration Removed when Configuring System Change By: Jason Davis Attachment: tool-saved.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41428) Tool Location Configuration Removed when Configuring System
Title: Message Title Jason Davis created an issue Jenkins / JENKINS-41428 Tool Location Configuration Removed when Configuring System Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud-plugin Created: 2017/Jan/25 2:37 PM Environment: Jenkins 2.32.1 vSphere Plugin 2.15 Git client Plugin 2.2.1 (but I've noticed that no tool location is kept) Priority: Major Reporter: Jason Davis I've noticed that the Tool Location configuration I've setup gets removed whenever anyone returns to edit the system configuration. Manage Jenkins -> Configure System Create a vSphere Cloud and Template In the template configuratnoi, check "Tool Locations" -> and provide a tool and path. In my case I'm overriding a git configuration I created with the Git client plugin in the Global Tool Configuration section called "git-default". I've noticed the effect occurs with other tools and it doesn't matter if you have multiple tools set here. Provide the path to the tool and save. The override I'm doing will show up in the generated templates after the agent is created and the jobs will pick up the tool override. Return to the "Configure System" page, scroll down and notice that the Tool Configuration information is no longer present. If you save at this point, the tool override value is lost. The big ugly hassle is we have a lot of systems now using templates and jobs
[JIRA] (JENKINS-40608) Job Summary Of Changes disappeared in version 1.4.12
Title: Message Title Jason Davis commented on JENKINS-40608 Re: Job Summary Of Changes disappeared in version 1.4.12 FYI - Don't have any pipeline jobs that would work, but I was unable to reproduce this problem with regular freestyle jobs on a jenkins I upgraded to 2.32.1 and P4 plugin I upgraded from 1.4.8 to 1.4.12. The changes report for job shows the list of changes all the way back through the entire history. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39798) System env not available for polled or triggered jobs
Title: Message Title Jason Davis commented on JENKINS-39798 Re: System env not available for polled or triggered jobs Ah OK - thanks for the clarification. In Jenkins, a master really defines a pretty unique node - it's the default name of the agent that is made available on the Jenkins server. Typically you don't want to build on your master agent/server, so folks add extra agents - or nodes - via separate build servers to spread the load and build redundancy. The server then routes the jobs based on labels, etc. you add to the agent/node definitions. Even with multiple masters, which would mean multiple Jenkins servers, it's really kind of a pain have multiple jenkins agents on the same build server - so I would say in 99.99% of the cases, JOB_NAME + NODE_NAME will result in a unique workspace definition name in an organization. And if it didn't, well, then you can just force sync the workspace when the job builds. You kind of have to do that anyway if your workspace is configured in the Jenkins job (which let's you use JOB_NAME, etc.) and/or your build is allowed to float across multiple build servers via labels. My two cents, adding support for COMPUTERNAME in the workspace spec via the job definition would be a very low priority enhancement vs. bug, since that's really not standard practice and not something typically possible in the Jenkins job/plugin configuration. 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
[JIRA] (JENKINS-39798) System env not available for polled or triggered jobs
Title: Message Title Jason Davis commented on JENKINS-39798 Re: System env not available for polled or triggered jobs Interesting, I'm kind of surprised you got COMPUTERNAME to resolve at all since system environment variables on the node or master are typically not available to the various plugin configurations used in Jenkins jobs. You can certainly use system environment variables in Shell and .bat build steps, but those are resolved when they run. Are you defining your workspace name in the Perforce job configuration? Also interesting, do you need both node and computername to unique-ify the workspace name? Won't those two values always be the same anyway the jobs on that Jenkins? On the surface, it'd seem job and node would be enough. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38140) Update relevant Jira issues doesn't work on downstream builds
Title: Message Title Jason Davis commented on JENKINS-38140 Re: Update relevant Jira issues doesn't work on downstream builds The break occurred between version 2.1 (working) and 2.2 (feature broken). Rolling back to 2.1 helps with using fingerprints to mark issues from upstream jobs, but then we lose the built-in ability to mark JIRA issues with pipelines. I tested with Jenkins 2.30, but assume it would work with 2.19 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38140) Update relevant Jira issues doesn't work on downstream builds
Title: Message Title Jason Davis commented on JENKINS-38140 Re: Update relevant Jira issues doesn't work on downstream builds Anyone happen to know if this is working in current builds of Jenkins? I have 2.25 asnd 2.30 in place with JIRA plugin 2.2.1 and I've noticed that downstream builds that used to rely and mark JIRA issues based on fingerprinted files are no longer marking the issues as they used to. This is a pretty serious problem for my group - we have rollup packages that pull built components and this feature helps announce to folks what's been fixed in those rollup packages. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38140) Update relevant Jira issues doesn't work on downstream builds
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-38140 Update relevant Jira issues doesn't work on downstream builds Change By: Jason Davis Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37503) Add Pipeline Support for ArtifactDeployer
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-37503 Add Pipeline Support for ArtifactDeployer Change By: Jason Davis Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38401) Jekinsfile Changelist nr doesn't get updated when using pipeline Script from SCM.
Title: Message Title Jason Davis commented on JENKINS-38401 Re: Jekinsfile Changelist nr doesn't get updated when using pipeline Script from SCM. Also running into this - the changes list for the build is never reset to only include the changes in that build, so it continually grows - making the list impractical for users to follow. Ideally - show only the Perforce changes in the build, and if there are no changes in the build, show "No Changes" rather than using the successful changes list from the previous build. Another problem side effect, when using the JIRA issue updater plugin to update JIRA tickets, the plugin is repeatedly marking JIRA issues, it looks like because the changes list is not being reset per build. So every build - even though there were no Perforce changes in that build - is marking the same JIRA issues in that list. I've had to avoid using my pipeline job, to avoid frustrating and confusing users. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37503) Add Pipeline Support for ArtifactDeployer
Title: Message Title Jason Davis commented on JENKINS-37503 Re: Add Pipeline Support for ArtifactDeployer Just trying to understand, it sounds like there currently isn't a way to post to remote shares and still build the "Last Successful Deployed Artifacts" link in the Jenkins job pages with the plugin. Is that true? For me, very few of the jobs utilize maven and everyone I support is used to seeing remote artifacts deployed in the Freestyle jobs and then downloading artifacts using the "Last Successful Deployed Artifacts" links the plugin creates in the Job pages. If I can't replicate that in a pipeline, this becomes a blocker, because I can't convert the jobs from Freestyle ones. I really don't want to use the built-in Archive the Artifacts" step, because this plugin's great advantage over that feature, is that big installers, etc. can be posted to a separate server and not on the Jenkins master which for me will seriously increase the storage/backup requirements for the master. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29075) List of changes escapes HTML output of jira-plugin
Title: Message Title Jason Davis edited a comment on JENKINS-29075 Re: List of changes escapes HTML output of jira-plugin I've noticed this issue with the P4 plugin. The overall project changes list is OK, but the change report for a single build is still showing the html for the link instead of actually showing the link. !p4-changes.png|thumbnail!jenkins 2.25, JIRA plugin 2.2.1, p4 plugin 1.4.8 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29075) List of changes escapes HTML output of jira-plugin
Title: Message Title Jason Davis commented on JENKINS-29075 Re: List of changes escapes HTML output of jira-plugin I've noticed this issue with the P4 plugin. The overall project changes list is OK, but the change report for a single build is still showing the html for the link instead of actually showing the link. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29075) List of changes escapes HTML output of jira-plugin
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-29075 List of changes escapes HTML output of jira-plugin Change By: Jason Davis Attachment: p4-changes.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis closed an issue as Fixed Fixed in 1.4.8. Thank you! Jenkins / JENKINS-36883 Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Change By: Jason Davis Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis edited a comment on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Fixed Verified fixed in 1.4.8. Thank you! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Hi Paul - I agree with you that the polling filter should only prevent builds from occurring on the changes in the filter path! That feature is working wonderfully, but there’s something else going on that’s causing files in the workspace spec to be sync’ed to _different _changelist levels after the Jenkins Quiet Period - and that started happening with v1.3.9 of the plugin. Up through 1.3.8, ALL files in a workspace spec did sync to the latest CL after a Quiet Period at build start time (without @now) – but that’s not happening any longer. Please see the above example. I explain there that, right now and without the use of @now in the workspace spec or P4 label setting, non-filtered files are currently being sync'ed to latest (CL 105), while filtered files are being sync'ed to trigger level (CL 100 instead of CL 103). I’ve confirmed this by testing with the above spec in a simple Jenkins job. Just make some checkins to files both in and out of a filtered path during a Quiet Period to see that they’re not synced to the latest CL at build start time. You suggested above in the Sept. 8 comment, that the build should sync to the CL at trigger time - not the CL at start time, so that other changes don't sneak in to the changes report. Also that @now should be used as a workaround. I’m further suggesting that @now shouldn’t be required to make the filtered files sync to latest at build start, because Jenkins has a configurable Quiet Period setting, which by design is to enable Devs to submit other changes after a trigger as an "oops" measure. If @now becomes required in the P4 Plugin label field or workspace spec to sync to latest after a Quiet Period, then that prevents use of other P4 labels I might like to use, essentially states that more configuration is required to use the Jenkins Quiet Period setting, would make the P4 plugin work by differently than all other SCM plugins I’m familiar with since I started using Jenkins around 8-9 years ago (TFS, SVN, Community Perforce), and the P4 plugin itself did not have this requirement until v1.3.9. In the end, I'm first hoping that ALL the files in the workspace spec are synced to the same and latest CL at build start time like it once did (and that’s the same CL that the changes also report uses) – and second, that the build should not require @now to deal with those changes checked in during the Jenkins Quiet Period because I believe that alters what one would expect from SCM plugins when using a Quiet Period (as well as other reasons mentioned in the above comments). Add Comment
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis reopened an issue Please - before closing - reconsider that not syncing all files in a workspace spec to latest by default goes philosophically against the quiet period, and that currently (without the now label), the build is syncing non-filtered files to the latest changelist, while filtered files in the workspace spec are syncing to a different, earlier changelist, which is not the same behavior (tried to explain better in my last comment). Jenkins / JENKINS-36883 Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Change By: Jason Davis Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title
Jason Davis commented on JENKINS-36883
Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
OK - however, I'm not certain this is a good fix for the problem. Changes after a trigger should be allowed during a quiet period without requiring the now label - not doing so thwarts the purpose of having a quiet period in Jenkins. Additionally, files are in fact being synced to different changeset levels at build start time. For ex. here's a contrived workspace spec in Jenkins: //SCM/Tools/Test/... //$ {JOB_NAME}/SCM/Tools/Test/... "//SCM/buildinfo/..." "//${JOB_NAME} /buildinfo/..." then I "Exclude Changes from Depot Path" with this: //SCM/buildinfo Next:
A build is triggered by a change under //SCM/Tools/Test, let's say with changeset 100.
Quiet period starts. During the quiet period, changes 101 through 105 are checked in, with 103 being the last change in the /buildinfo/... path and 105 being the last change under the Tools/Test/... path
The quiet period ends.
The build launches - the latest available changeset for the workspace is 105. What is occurring is that the build is sync'ing the files changed during the quiet period under Tools/Test/... to changeset 105 and the files changed under buildinfo/... to changeset 100. I've confirmed this with a simple Jenkins job using the above spec and a quiet period. This is inconsistent - the files in buildinfo/... should be synced to the latest changeset for the whole workspace (105) at build time without the use of the now label, or everything should be synced to changeset 100, however, I'd argue syncing to changeset 100 would runs against the purpose of the quiet period AND is not what occurred through v1.3.8 of the plugin: all files in the workspace spec were synced to the latest at build time.
My hope is that everything in the workspace spec would be synced to the latest at build time (unless you use Polling per Change), because that would be consistent no matter how the build was launched.
Add Comment
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Thanks a ton for working on this! It sounds like perhaps the change was to enable 'now' work as a label after a quiet period. Is that the only change in the works, or will exclude filtered files now also be synced to the latest change without the label? I could update all my jobs to use 'now', but then I'd have to use that by default when using the plugin (to accommodate the excluded files + quiet period problem) and it makes me wonder what I should do if I ever need to use the plugin with a different label other than 'now'. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Paul Allen - hope the conference was a good one for you. Just curious if I helped make the issue more clear. Fingers crossed that you have time to take a look and help (I think it's just a problem with files in the excluded list not syncing to the latest due to the quiet period). If I can test or do anything, just let me know. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Tested pinning the build to a label with both 'now' and '@now' with v1.4.6. Unfortunately, still getting the same behavior - files in the exclude changes filter are not being sync'ed to the latest changeset if additional changes are checked in during the quiet period, but the other files in the view are. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Thanks for taking a look! I have not tried the pin label to 'now' idea (that idea just didn't dawn on me. ), but I'll give that a try ASAP and let you know. I can understand your point of view for knowing what triggered the build, but at the same time, when the build finally fires off after a quiet period, just taking the latest available change when the build finally fires off, and tracking _that _for the changes summary, I would suggest makes sense also. Say there was no quiet period or polling. If someone pushed the build now button, Perforce would gather the latest changeset at that moment and sync to that level. Polling without a quiet period also ends up syncing to the latest available changeset at build launch. It's the addition of the quiet period that is leading to different behavior, because other changes checked in after the trigger, but before the build launches (which of course is one purpose for the quiet period - in case the Devs have an "oh crap! I forgot to check that in also" moment) are being sync'ed to changeset that triggered the build, not the latest. If - no matter how you triggered the build - the build always synced and tracked to the latest changeset, the summary would be consistent no matter how the build is launched. This would be how the community plugin worked and the P4 plugin worked up through 1.3.8. It also maintains the purpose of the quiet period, otherwise the "oh crap!" changes never make it into the build, because they are checked in after the trigger changeset. Also – and this is the big thing that threw me off – it's only the files that are in the "Exclude Changes" filter that are being sync'ed to the trigger changeset level. Normal files in the view, but not in the Exclude Changes filter, are being synced to the latest available changeset at build launch. In my environment, more changes are often checked in during the quiet period, and unfortunately, the way our builds communicate, those Exclude Changes files must be the latest available at build launch time, or hell breaks loose. Thanks and hope you enjoy the conference! Add Comment
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis edited a comment on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Unfortunately, syncing to latest is still not working in version 1.4.6. Also tried the new option to "Exclude changes outside view mask" and that too also left me with files outside the view mask that were not synced to the latest at build time. Files within the mask do sync to the latest are being synced to the latest if subsequent check-ins occur during the quiet period. I just don't understand how not syncing (even the filtered paths) to the latest at build time is expected behavior. If I could fix this on my own I would... Something in 1.3.9 that wasn't considered? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Unfortunately, syncing to latest is still not working in version 1.4.6. Also tried the new option to "Exclude changes outside view mask" and that too also left me with files outside the view mask that were not synced to the latest at build time. Files within the mask do sync to the latest are synced to the latest if subsequent check-ins occur during the quiet period. I just don't understand how not syncing (even the filtered paths) to the latest at build time is expected behavior. If I could fix this on my own I would... Something in 1.3.9 that wasn't considered? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Man - I was hoping that version 1.4.4's change for JENKINS-37124 was going to address this problem also, but files in the "exclude changes..." list are still being synced to the triggered changelist number and not the latest available changelist. It's a bummer, because I'd like to stay in sync with the other fixes, improvements, and changes for building pipelines. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-36883 Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Change By: Jason Davis Environment: P4 2015.2 (Win 2008 R@), Jenkins 2.14 (Win 2008 R2), P4-Plugin 1.4.3 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34924) p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace
Title: Message Title Jason Davis commented on JENKINS-34924 Re: p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace Ben Langton - I tested with the workaround to see if it might help my issue also, but unfortunately I'm still getting the same behavior syncing filtered files. Much appreciated though! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Possibly also related to: JENKINS-33484 - P4 sync on triggered builds ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34924) p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace
Title: Message Title Jason Davis commented on JENKINS-34924 Re: p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace After more testing with 1.4.3 I was able to more readily track down the problem I was experiencing. This issue still sounds like it's related, but it's not seemingly the same as described here, so I logged a new issue for tracking there: JENKINS-36883 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis created an issue Jenkins / JENKINS-36883 Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2016/Jul/22 6:37 PM Priority: Major Reporter: Jason Davis I’ve found that the latest versions of files that are mapped in a workspace and also in an “Exclude changes from Depot path” polling filter, are not being synced at build time. Here’s the scenario. I’m currently set Jobs to use Manual workspaces set in Jenkins, to do a Force Sync, and have the “Populate have list” flag set. The Workspace includes an example path: PathA/… PathB/… Also configured with the Polling Filter - “Exclude changes from Depot path” is set to a path under PathB (actually in my test it was the same path). What happens: A check-in under Path A is recognized from polling and triggers a build which has a quiet period associated with it. During the quiet period, one or more check-ins occur under Path B. These files naturally have a higher changelist number than what triggered the build. When the quiet period expires, the build starts and syncs Path A’s files to latest available changelist for that Path, whatever it may be – All is good! For the files in Path B, however, the build syncs to the changelist number from Path A that triggered the build, NOT the latest available changelist. That causes the files under Path B, to be sync’ed to non-latest state. Again, if check-ins occur in the quiet period under Path A – the latest versions of those files ARE being synced.
[JIRA] (JENKINS-36426) How to poll two different folder under a single branch in single job
Title: Message Title
Jason Davis edited a comment on JENKINS-36426
Re: How to poll two different folder under a single branch in single job
You could just create a workspace that has the folders you want and either manage that in P4V or in Jenkins. Personally, I'd rather have a different workspace tuned for what I want rather than sharing it, just so I know the purpose of the workspace. For me, I like to keep the workspaces in Jenkins, so I set the Perforce config in the Job to "Manual", then set the name to ${JOB_NAME}, then I'd set the view mappings to: {noformat} //OSSLEV3/Dev_R4/Cramer/... //${JOB_NAME}/...//OSSLEV3/Dev_R4/MNGP/... //${JOB_NAME}/... {noformat} Jenkins will automatically create a workspace for you with the name of your Jenkins job. btw - Perforce by default doesn't like mapping two different depot paths to the same place, leading to a similar problem you've described. To get around that you'll probably need to use overlay mappings.https://www.perforce.com/perforce/doc.current/manuals/p4guide/chapter.configuration.html#configuration.refine_workspace.map_diff_depot_locationsLeading to something like this: {noformat} //OSSLEV3/Dev_R4/Cramer/... //${JOB_NAME}/...+//OSSLEV3/Dev_R4/MNGP/... //${JOB_NAME}/... |Col A2| {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36426) How to poll two different folder under a single branch in single job
Title: Message Title
Jason Davis edited a comment on JENKINS-36426
Re: How to poll two different folder under a single branch in single job
You could just create a workspace that has the folders you want and either manage that in P4V or in Jenkins. Personally, I'd rather have a different workspace tuned for what I want rather than sharing it, just so I know the purpose of the workspace. For me, I like to keep the workspaces in Jenkins, so I set the Perforce config in the Job to "Manual", then set the name to ${JOB_NAME}, then I'd set the view mappings to://OSSLEV3/Dev_R4/Cramer/... //${JOB_NAME}/...//OSSLEV3/Dev_R4/MNGP/... //${JOB_NAME}/...Jenkins will automatically create a workspace for you with the name of your Jenkins job. btw - Perforce by default doesn't like mapping two different depot paths to the same place, leading to a similar problem you've described. To get around that you'll probably need to use overlay mappings.https://www.perforce.com/perforce/doc.current/manuals/p4guide/chapter.configuration.html#configuration.refine_workspace.map_diff_depot_locationsLeading to something like this://OSSLEV3/Dev_R4/Cramer/... //${JOB_NAME}/...+//OSSLEV3/Dev_R4/MNGP/... //${JOB_NAME}/... |Col A2|
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36426) How to poll two different folder under a single branch in single job
Title: Message Title
Jason Davis edited a comment on JENKINS-36426
Re: How to poll two different folder under a single branch in single job
You could just create a workspace that has the folders you want and either manage that in P4V or in Jenkins. Personally, I'd rather have a different workspace tuned for what I want rather than sharing it, just so I know the purpose of the workspace. For me, I like to keep the workspaces in Jenkins, so I set the Perforce config in the Job to "Manual", then set the name to ${JOB_NAME}, then I'd set the view mappings to: {noformat} //OSSLEV3/Dev_R4/Cramer/... //${JOB_NAME}/...//OSSLEV3/Dev_R4/MNGP/... //${JOB_NAME}/... {noformat} Jenkins will automatically create a workspace for you with the name of your Jenkins job. btw - Perforce by default doesn't like mapping two different depot paths to the same place, leading to a similar problem you've described. To get around that you'll probably need to use overlay mappings.https://www.perforce.com/perforce/doc.current/manuals/p4guide/chapter.configuration.html#configuration.refine_workspace.map_diff_depot_locationsLeading to something like this: {noformat} //OSSLEV3/Dev_R4/Cramer/... //${JOB_NAME}/...+//OSSLEV3/Dev_R4/MNGP/... //${JOB_NAME}/... {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36426) How to poll two different folder under a single branch in single job
Title: Message Title
Jason Davis commented on JENKINS-36426
Re: How to poll two different folder under a single branch in single job
You could just create a workspace that has the folders you want and either manage that in P4V or in Jenkins. Personally, I'd rather have a different workspace tuned for what I want rather than sharing it, just so I know the purpose of the workspace. For me, I like to keep the workspaces in Jenkins, so I set the Perforce config in the Job to "Manual", then set the name to $ {JOB_NAME}, then I'd set the view mappings to: //OSSLEV3/Dev_R4/Cramer/... //${JOB_NAME} /... //OSSLEV3/Dev_R4/MNGP/... //$ {JOB_NAME}/... Jenkins will automatically create a workspace for you with the name of your Jenkins job. btw - Perforce by default doesn't like mapping two different depot paths to the same place, leading to a similar problem you've described. To get around that you'll probably need to use overlay mappings. https://www.perforce.com/perforce/doc.current/manuals/p4guide/chapter.configuration.html#configuration.refine_workspace.map_diff_depot_locations Leading to something like this: //OSSLEV3/Dev_R4/Cramer/... //${JOB_NAME} /... +//OSSLEV3/Dev_R4/MNGP/... //$ {JOB_NAME} /...
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34924) p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace
Title: Message Title Jason Davis commented on JENKINS-34924 Re: p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace Hi there - just curious if this issue has been considered recently. I'd love to upgrade from 1.3.8, but this issue is actually a blocker since I can't achieve a good build without getting the latest files available when the build actually starts. It looks like maybe this change in 1.4.2 might help, but it's difficult to know. "Add checks for sync CL and head CL" 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] [p4-plugin] (JENKINS-34924) p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace
Title: Message Title Jason Davis edited a comment on JENKINS-34924 Re: p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace I came to log a possibly related bug in 1.3.9 - or what sounds like another side effect of this noticed problem. If it's not related, I'd be happy to create a new issue. In my case, I'm doing a clean workspace wipe and force sync and I want the build to sync to the latest revision when the job finally kicks off and builds, however, the build is NOT syncing to the latest available change, it's instead syncing to the latest available change that triggered the build.What appears to be happening is that when the build is polling for changes and when it finds one it enters the queue and starts to build. If another build is triggered by a change while the first is building, the second build appears to remember the change that triggered itself and then sync to that level. That makes some sense, but there may be many other changes that are checked after the point the job enters the queue while it waits. Those other changes are not being synced when the second build finally starts. For me this is causing multiple problems, it's confusing users, because they expect their changes in the build that initiated after their checkin and not all of them are showing up. Additionally, in my environment, builds are actually doing some updates on files and checking those into perforce for subsequent builds. Because in some cases those updates are occurring after the second build is triggered, the second build is syncing the previous version of those files and causing a reconcile situation when it tries to submit it's own config changes to perforce. The reconcile step is causing all sorts of builds to fail and folks think that there's something corrupted with Jenkins, the process, or the build workspace. :-(Rolling back to 1.3.8 seems to fix fixed the problem and enable enabled the build to sync to the latest change (not 100% sure yet) , but if syncing to the change that triggered a build is by design, then it appears I need a "sync to latest available change at build time" option in the plugin configuration, or I'll have to come up with a new way to manage my builds.In case it matters, I'm also syncing multiple top level depot paths with a manual workspace view set in the job definition and setting the three populate options: populate have list, sync with modtime, and quiet messages. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [p4-plugin] (JENKINS-34924) p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace
Title: Message Title Jason Davis commented on JENKINS-34924 Re: p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace I came to log a possibly related bug in 1.3.9 - or what sounds like another side effect of this noticed problem. If it's not related, I'd be happy to create a new issue. In my case, I'm doing a clean workspace wipe and force sync and I want the build to sync to the latest revision when the job finally kicks off and builds, however, the build is NOT syncing to the latest available change, it's instead syncing to the latest available change that triggered the build. What appears to be happening is that when the build is polling for changes and when it finds one it enters the queue and starts to build. If another build is triggered by a change while the first is building, the second build appears to remember the change that triggered itself and then sync to that level. That makes some sense, but there may be many other changes that are checked after the point the job enters the queue while it waits. Those other changes are not being synced when the second build finally starts. For me this is causing multiple problems, it's confusing users, because they expect their changes in the build that initiated after their checkin and not all of them are showing up. Additionally, in my environment, builds are actually doing some updates on files and checking those into perforce for subsequent builds. Because in some cases those updates are occurring after the second build is triggered, the second build is syncing the previous version of those files and causing a reconcile situation when it tries to submit it's own config changes to perforce. The reconcile step is causing all sorts of builds to fail and folks think that there's something corrupted with Jenkins, the process, or the build workspace. Rolling back to 1.3.8 seems to fix the problem and enable the build to sync to the latest change (not 100% sure yet), but if syncing to the change that triggered a build is by design, then it appears I need a "sync to latest available change at build time" option in the plugin configuration, or I'll have to come up with a new way to manage my builds. In case it matters, I'm also syncing multiple top level depot paths with a manual workspace view set in the job definition and setting the three populate options: populate have list, sync with modtime, and quiet messages. Add Comment
[JIRA] [p4-plugin] (JENKINS-34916) Parallel Sync - Accept Global or Node Variables
Title: Message Title
Jason Davis created an issue
Jenkins / JENKINS-34916
Parallel Sync - Accept Global or Node Variables
Issue Type:
New Feature
Assignee:
Unassigned
Components:
p4-plugin
Created:
2016/May/18 1:28 PM
Environment:
1.3.9 p4 plugin jenkins 2.5
Priority:
Minor
Reporter:
Jason Davis
For the new parallel sync option, I tried providing the path to p4.exe as a Global Variable (ex. $ {WIN_P4_PATH}
) and found the plugin didn't appear to expand the variable and find the executable.
Could this section also accept a variable - set either at the System or Node level - so this information could be centralized and managed above the job?
Thanks
[JIRA] [perforce-plugin] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?
Title: Message Title Jason Davis closed an issue as Fixed Jenkins / JENKINS-17652 Poll Exclude Files Too Aggressive on Blocking Builds? Change By: Jason Davis Status: Resolved Closed 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] [junit-plugin] (JENKINS-25649) Duplicate Test Reports in Projects
Title: Message Title Jason Davis closed an issue as Duplicate Jenkins / JENKINS-25649 Duplicate Test Reports in Projects Change By: Jason Davis Status: Resolved Closed 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] [p4-plugin] (JENKINS-25145) Version Jenkins Configuration In Perforce
Title: Message Title Jason Davis commented on JENKINS-25145 Re: Version Jenkins Configuration In Perforce Don't know if this fully applies, but the Job Config History Plugin can help. https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin Also, the new Workflow/Pipeline plugin (which really appears to be the way of the future in Jenkins land) has the ability to store the entire job in source - this might work out to also bring along the Perforce config into source also if the job is a workflow and the Perforce plugin supports this feature. See Pipeline script from SCM on this page and the Multibranch comments. https://github.com/jenkinsci/workflow-plugin/blob/master/TUTORIAL.md More on Multibranch - don't know if this Perforce plugin supports a multibranch type setup, but if it did, it would be sweet! https://jenkins-ci.org/blog/2015/12/03/pipeline-as-code-with-multibranch-workflows-in-jenkins/ 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] [p4-plugin] (JENKINS-32368) Changes list is not showing the correct changes in a build
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-32368 Changes list is not showing the correct changes in a build Change By: Jason Davis When viewing the overall project changes list, the list of actual perforce changes being shown appears to be the list of every change since the build started. It should show only the list of changes in the given build, regardless if the build failed, was aborted, succeeded, etc. In the attached screenshot build #127 had only one change, but it's showing the previous 8, build 126 had two changes, but it's showing the previous 8, etc.The incorrect list is also appearing in the individual build's changes list.My users are definitely giving me a hard time about this because they can't easily tell what's in a build. This is making it impossible to choose this plugin over the older/original Perforce plugin which doesn't exhibit this problem - even though I would rather because of your support, swarm integration, the need to not install the p4 client on the build node, etc. It also makes using Perforce itself problematic, because the SVN and Git plugins don't have this problem and folks just don't understand or care about the difference between plugin and tools. Don't know yet if this issue is just a side effect of JENKINS-30868 - if so, sorry for the duped ticket. 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
[JIRA] [p4-plugin] (JENKINS-32368) Changes list is not showing the correct changes in a build
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-32368 Changes list is not showing the correct changes in a build Change By: Jason Davis Attachment: changeslist-build.png 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] [p4-plugin] (JENKINS-32368) Changes list is not showing the correct changes in a build
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-32368 Changes list is not showing the correct changes in a build Change By: Jason Davis When viewing the overall project changes list, the list of actual perforce changes being shown appears to be the list of every change since the build started. It should show only the list of changes in the given build, regardless if the build failed, was aborted, succeeded, etc. In the attached screenshot build #127 had only one change, but it's showing the previous 8, build 126 had two changes, but it's showing the previous 8, etc. The incorrect list is also appearing in the individual build's changes list. My users are definitely giving me a hard time about this because they can't easily tell what's in a build. This is making it impossible to choose this plugin over the older/original Perforce plugin which doesn't exhibit this problem - even though I would rather because of your support, swarm integration, the need to not install the p4 client on the build node, etc. It also makes using Perforce itself problematic, because the SVN and Git plugins don't have this problem and folks just don't understand or care about the difference between plugin and tools. 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
[JIRA] [p4-plugin] (JENKINS-31083) Performance issue when querying changelog information
Title: Message Title Jason Davis commented on JENKINS-31083 Re: Performance issue when querying changelog information We've noticed the same behavior with performance when clicking on the changes link. We thought it might be because it appears the changes per build aren't currently reflecting what's actually in the build (creating a different ticket for that). We have decent VM with a replica close our our build systems, so it's unclear, other than the explanation here, why there would be a delay when using the various build or project "changes" link. 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] [p4-plugin] (JENKINS-32368) Changes list is not showing the correct changes in a build
Title: Message Title Jason Davis created an issue Jenkins / JENKINS-32368 Changes list is not showing the correct changes in a build Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 08/Jan/16 5:38 PM Environment: Jenkins 1.6.42 p4-plugin 1.3.4 Priority: Major Reporter: Jason Davis When viewing the overall project changes list, the list of actual perforce changes being shown appears to be the list of every change since the build started. It should show only the list of changes in the given build, regardless if the build failed, was aborted, succeeded, etc. In the attached screenshot build #127 had only one change, but it's showing the previous 8, build 126 had two changes, but it's showing the previous 8, etc. My users are definitely giving me a hard time about this because they can't easily tell what's in a build. This is making it impossible to choose this plugin over the older/original Perforce plugin which doesn't exhibit this problem - even though I would rather because of your support, swarm integration, the need to not install the p4 client on the build node, etc. It also makes using Perforce itself problematic, because the SVN and Git plugins don't have this problem and folks just don't understand or care about the difference between plugin and tools.
[JIRA] [p4-plugin] (JENKINS-32368) Changes list is not showing the correct changes in a build
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-32368 Changes list is not showing the correct changes in a build Change By: Jason Davis Attachment: changeslist.png 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] [p4-plugin] (JENKINS-30868) Changes List in Project and Job is Displaying Last Change
Title: Message Title Jason Davis commented on JENKINS-30868 Re: Changes List in Project and Job is Displaying Last Change Just found a new wrinkle - I had a build post all the changes since the beginning of the workspace in addition to stating the build included changes from the previous build when there were no changes in between builds (screenshot 3). I have no explanation why the second to last build did this, there have been no configuration changes other than updating to the latest build of the P4 plugin and jenkins before that build. The latest build is still showing the last change from the previous build. 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] [p4-plugin] (JENKINS-30868) Changes List in Project and Job is Displaying Last Change
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-30868 Changes List in Project and Job is Displaying Last Change Change By: Jason Davis Attachment: screenshot-3.png 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] [p4-plugin] (JENKINS-30868) Changes List in Project and Job is Displaying Last Change
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-30868 Changes List in Project and Job is Displaying Last Change Change By: Jason Davis Environment: Jenkins 1.6. 31 32 P4Plugin 1.3. 1 2 Java 1.8.0_45-b15 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] [p4-plugin] (JENKINS-30868) Changes List in Project and Job is Displaying Last Change
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-30868 Changes List in Project and Job is Displaying Last Change Change By: Jason Davis Attachment: screenshot-2.png 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] [p4-plugin] (JENKINS-30868) Changes List in Project and Job is Displaying Last Change
Title: Message Title Jason Davis created an issue Jenkins / JENKINS-30868 Changes List in Project and Job is Displaying Last Change Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 09/Oct/15 6:08 PM Environment: Jenkins 1.6.31 P4Plugin 1.3.1 Java 1.8.0_45-b15 Priority: Major Reporter: Jason Davis I have some builds that are not being triggered by polling. They are being triggered by upstream jobs, but they still need to sync some files to do their thing. The builds are displaying the last change that was made in the workspace even though the change was previously synced and built in a much earlier build. The effect is that other builds are still occurring, and no changes have occurred, but the last change is being reported each and every build. Rather than showing the last change from a previous build, something like "No Changes" should be displayed for each build when there are no changes to report. Hopefully the screenshots explain the issue better than I do. Screenshot 2 shows build 27 was launched on Oct 9, but it reported a change that was made on May 6 - which would be fine if there had been no previous builds, but previous builds already sync'ed and reported that change (as shown in screenshot 1).
[JIRA] [p4-plugin] (JENKINS-30868) Changes List in Project and Job is Displaying Last Change
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-30868 Changes List in Project and Job is Displaying Last Change Change By: Jason Davis Attachment: screenshot-1.png 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] [p4-plugin] (JENKINS-28421) Information provided to email-ext should be perforce email address, not perforce username
Title: Message Title Jason Davis commented on JENKINS-28421 Re: Information provided to email-ext should be perforce email address, not perforce username I'm also in the same boat as A C and kind of a deal breaker for the plugin at the moment (don't get me wrong, the plugin is coming along real well). Collecting the email addresses from Perforce appears to be a feature of the other Perforce plugin in case that helps. 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] [p4-plugin] (JENKINS-25085) email-ext showPaths does not work with p4-plugin
Title: Message Title Jason Davis commented on JENKINS-25085 Re: email-ext showPaths does not work with p4-plugin I sort of disagree with this being a minor, but I also can't see myself making this a major. Long term, it's not practical to schlep around a groovy script in your environment and with email-ext all but the defacto standard for sharing info by email, something should be done to provide info to that option, because giving recipients a heads up on what actually was affected immediately in the email vs. looking it up has value. Agreed though - who needs 1000s of records in the email? Maybe the plugin could supply the first 20 paths to showpaths and mention on row 21 Only 20 paths shown, for additional info, review the changeset number in directly in Perforce... 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] [xunit-plugin] (JENKINS-25527) xUnit reports yield duplicated Test Result Trend charts
Jason Davis commented on JENKINS-25527 xUnit reports yield duplicated Test Result Trend charts Experiencing the same problem after upgrading to v1.92 (I only performed plugin upgrades) - however, I noticed the issue with existing reports. The duplicate chart appeared right after restarting Jenkins and before any builds occurred. I'm generating mstest results in a freestyle project on a windows host and slave. jenkins version is 1.585. Downgrading to v1.91 didn't help resolve the duplicate test result charts issue. 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] [xunit-plugin] (JENKINS-25527) xUnit reports yield duplicated Test Result Trend charts
Jason Davis edited a comment on JENKINS-25527 xUnit reports yield duplicated Test Result Trend charts Experiencing the same problem after upgrading to v1.92 (I only performed plugin upgrades) - however, I noticed the issue with existing reports. The duplicate chart appeared right after restarting Jenkins and before any builds occurred. I'm generating mstest results in a freestyle project on a windows host and slave. jenkins version is 1.585. Downgrading to v1.91 didn't help resolve the duplicate test result charts issue. - False alarm - just noticed the problem in another project not using xUnit and reverting the Junit plugin (which I had also upgraded) to the previous version 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/d/optout.
[JIRA] [junit-plugin] (JENKINS-25649) Duplicate Test Reports in Projects
Jason Davis created JENKINS-25649 Duplicate Test Reports in Projects Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 17/Nov/14 2:51 PM Description: Duplicate Test Results chart after upgrading to version 1.2. Reverting back to 1.1 resolved the issue. I'm seeing this in Test results generated in projects using the xUnit plugin and the HP Application Automation Tools plugin. Environment: Windows 2008 R2 - Jenkins 1.585 Project: Jenkins Priority: Minor Reporter: Jason Davis 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] [core] (JENKINS-5125) Block build when upstream is building option is not working with multiple executors
Jason Davis commented on JENKINS-5125 Block build when upstream is building option is not working with multiple executors Yes - 1.570 (Windows). Also left a comment in JENKINS-5150 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] [core] (JENKINS-5150) Race condition for feature Block build when upstream project is building
Jason Davis commented on JENKINS-5150 Race condition for feature Block build when upstream project is building I just experienced/noticed this issue in 1.570. I have an upstream project that was choked out for an extended period of time while downstream builds that are configured to be blocked by the upstream built anyway. The downstream builds entered the queue after the parent, but they built first. Additional, new downstream builds compounded the problem until checkins in those builds quieted down. In some cases, three builds of children that should have built after the parent built before they should have according to "Block build when upstream project is building" rules. 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] [perforce] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?
Jason Davis resolved JENKINS-17652 as Fixed Poll Exclude Files Too Aggressive on Blocking Builds? Looks like v1.3.22 has solved the issue. Files that were once NOT triggering the build - it looks like because of the spaces - are now triggering builds. Thank you much for your help! Change By: Jason Davis (01/May/13 1:18 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?
Jason Davis commented on JENKINS-17652 Poll Exclude Files Too Aggressive on Blocking Builds? Thank you much! I'll try it out and update the ticket when you release the next update. Thanks for a great plugin. 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] [perforce] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?
Jason Davis commented on JENKINS-17652 Poll Exclude Files Too Aggressive on Blocking Builds? I see. Yup - I definitely thought you meant the spec area in Jenkins for the exclude paths. There are no replacements in any of the Workspace specs that I've setup. One of them has a few eliminated mappings: -//apath/item/... and it looks like all of them have at least one quoted mapping "//a path/item/..." The mappings all also include files from more than one depot. The mappings in 95% of the builds exhibiting the problem look like this: //depot/item/item/... //SpecName/... "//depot2/path item/item1/..." "//SpecName/path item/item1/..." //depot2/path2/item2/... //SpecName/path2/item2/... I think those are the only slightly unusual thing that I have going on. Maybe this is helpful... It's files in the second depot that I'm excluding. However, I'm also making other checkins in that second depot that I would think would trigger the build, because they're not being excluded. The plugin appears to be determining them to be excluded anyway. 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] [perforce] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?
Jason Davis edited a comment on JENKINS-17652 Poll Exclude Files Too Aggressive on Blocking Builds? The excluded files and subdirs themselves only exist in the second depot. The first depot DOES have a similar upper portion of the path, however, we don't overlap the two in our Workspace specs. So yes, depot1 contains a similar set of upper paths and they diverge, but we don't map them together in the workspace. If we had mapped the two together, the actual excluded subdirs and files only exist in depot2 - there wouldn't be any collisions. So for ex. this exists in depot1 (the "ItemsX" share the same names in our Perforce): "//depot1/ITEMA/Item B/..." and depot2: "//ITEMA/Item B/newfoldernotinfirstdepot/config/buildinfo/..." ITEMA is the name of our second depot. 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] [perforce] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?
Jason Davis commented on JENKINS-17652 Poll Exclude Files Too Aggressive on Blocking Builds? Hmmm... I can't say for certain, because I didn't think to keep a history of the past polling issues, but for the 4 or so builds that should have built at this very moment - that is true. All the files have been mistakenly marked as being excluded are currently in a path with spaces. The files happen to share a common parent folder and I'm exluding files in the "buildinfo" folder. //depot2/Item Path1/path2/UTandCover.fbp7 (A checkin occurred on this file) The exclude spec has this: //depot2/Item Path1/path2/config/buildinfo/... 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] [perforce] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?
Jason Davis commented on JENKINS-17652 Poll Exclude Files Too Aggressive on Blocking Builds? Thanks again for checking this out. Yes - I'm just using depot paths. Also the standard matchers - no %1 or %2 type matching. The paths I'm using are just text paths. ex. //depot/item/path/item/... I just replaced them above in the examples to avoid showing some of the product information. In one case it's a full path to a file, in the other, it's all files in the directory using /... 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?
Jason Davis commented on JENKINS-17652 Poll Exclude Files Too Aggressive on Blocking Builds? Just checked polling on a build that has this single row in the exclude files section: //afilepath/VersionInfo.cs However the build is not being triggered when it finds changes in other paths: Exclude file(s) found: //asecondfilepath/ScriptBox/Help.fbp7 //asecondfilepath/LaunchChecker.fbp7 Changelist 185127 is composed of file(s) and/or user(s) that are excluded. Is it correct that even if VersionInfo.cs was in the list of excluded files, these changes should still trigger a build? btw - In this actual build, VersionInfo.cs isn't even in the list of changes that the build is currently aware of. 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] [perforce] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?
Jason Davis commented on JENKINS-17652 Poll Exclude Files Too Aggressive on Blocking Builds? Thank you for the clarification. Neither asecondfilepath nor afilepath include non-alphanumeric characters. The paths are in completely separate locations in the source tree sharing only the topmost level of the path. asecondfilepath does contain a space so I have to quote the path in the exclude list. Thanks for looking into this! 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] [perforce] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?
Jason Davis commented on JENKINS-17652 Poll Exclude Files Too Aggressive on Blocking Builds? Yes - I did and unfortunately the files I'm trying to exclude have spaces in the Perforce path. When I take away the quotes, I'm warned about the path not being a valid Perforce path and it looks like Polling stops altogether. I tested this with another project that was just excluding files in this path: "//asecondfilepath/config/buildinfo/..." I just took this path out of another build and left only: //afilepath/VersionInfo.cs in the exclude files section, but I'll have to wait for awhile for to see if the exclusions work and if it's quoted Perforce paths causing 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] [perforce] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?
Jason Davis edited a comment on JENKINS-17652 Poll Exclude Files Too Aggressive on Blocking Builds? Yes - I just now did and unfortunately the files I'm trying to exclude have spaces in the Perforce path. When I take away the quotes, I'm warned about the path not being a valid Perforce path and it looks like Polling stops altogether. I tested this with another project that was only excluding files in this path: "//asecondfilepath/config/buildinfo/..." To possibly test if quoted Perforce paths are what's causing the problem, I also just now took the above path out of another build and left only: //afilepath/VersionInfo.cs in the exclude files section. I'll have to wait for awhile to see if the exclusions start allowing build through again. 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] [perforce] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?
Jason Davis edited a comment on JENKINS-17652 Poll Exclude Files Too Aggressive on Blocking Builds? Yes - I just now did and unfortunately the files I'm trying to exclude have spaces in the Perforce path. When I take away the quotes, I'm warned about the path not being a valid Perforce path and it looks like Polling stops altogether. I tested this with another project that was only excluding files in this path: "//asecondfilepath/config/buildinfo/..." To possibly test if quoted Perforce paths are what's causing the problem, I also just now took the above path out of another build and left only: //afilepath/VersionInfo.cs in the exclude files section. I'll have to wait for awhile to see if the exclusions start allowing builds through again. 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] [perforce] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?
Jason Davis created JENKINS-17652 Poll Exclude Files Too Aggressive on Blocking Builds? Issue Type: Bug Affects Versions: current Assignee: Rob Petti Components: perforce Created: 17/Apr/13 12:40 PM Description: Caveat - It's definitely possible that I don't understand how Poll Exclude Files should work. It seems like changes that should trigger a build when Poll Exclude Files are provided are not. I currently have this in my Poll Exclude Files section (all paths are in the Client Spec): //afilepath/VersionInfo.cs //afilepath/VersionInfo.rc2 "//asecondfilepath/config/buildinfo/..." Below is the polling log for one of my builds. I would have expected that CS 184776 would have triggered the build, however, polling reports that it is an excluded file. Exclude file(s) found: //asecondfilepath/UTandCover.fbp7 Changelist 184776 is composed of file(s) and/or user(s) that are excluded. I thought I had excluded all "buildinfo/..." files which are in a different subdirectory, but maybe I can't exclude files when they are in the same root dir? Thanks -- Started on Apr 17, 2013 8:04:53 AM Looking for changes... Using node: blah Using remote perforce client: blah jenkins $ "C:\Program Files\Perforce\p4.exe" workspace -o blah 'Don't update client' is set. Not saving the client changes. jenkins $ "C:\Program Files\Perforce\p4.exe" counter change jenkins $ "C:\Program Files\Perforce\p4.exe" -s changes -s submitted //blah/...@184734,@184829 Latest submitted change selected by workspace is 184807 jenkins $ "C:\Program Files\Perforce\p4.exe" describe -s 184807 jenkins $ "C:\Program Files\Perforce\p4.exe" -G where //... Exclude file(s) found: //afilepath/VersionInfo.rc2 Changelist 184807 is composed of file(s) and/or user(s) that are excluded. jenkins $ "C:\Program Files\Perforce\p4.exe" describe -s 184806 Exclude file(s) found: //afilepath/VersionInfo.cs Changelist 184806 is composed of file(s) and/or user(s) that are excluded. jenkins $ "C:\Program Files\Perforce\p4.exe" describe -s 184776 Exclude file(s) found: //asecondfilepath/UTandCover.fbp7 Changelist 184776 is composed of file(s) and/or user(s) that are excluded. jenkins $ "C:\Program Files\Perforce\p4.exe" describe -s 184754 Exclude file(s) found: //asecondfilepath/config/buildinfo/Item3.17.0.0.buildinfo Changelist 184754 is composed of file(s) and/or user(s) that are excluded. jenkins $ "C:\Program Files\Perforce\p4.exe" describe -s 184751 Exclude file(s) found: //asecondfilepath/config/buildinfo/Item2.17.0.0.buildinfo Changelist 184751 is composed of file(s) and/or user(s) that are excluded. jenkins $ "C:\Program Files\Perforce\p4.exe" describe -s 184748 Exclude file(s) found: //asecondfilepath/config/buildinfo/Item1.17.0.0.buildinfo Changelist 184748 is composed of file(s) and/or user(s) that are excluded. jenkins $ "C:\Program Files\Perforce\p4.exe" describe -s 184746 Exclude file(s) found: //afilepath/VersionInfo.rc2 Changelist 184746 is composed of file(s) and/or user(s) that are excluded. jenkins $ "C:\Program Files\Perforce\p4.exe" describe -s 184745 Exclude file(s) found: //afilepath/VersionInfo.cs Changelist 184745 is composed of file(s) and/or user(s) that are excluded. Done. Took 5.9 sec No changes Environment: Jenkins: 1.511 Perforce Server Version: 2012.1 Java 1.7.0_17 Perforce Plugin: 1.3.21 Server: Windows 2008 R2 Project: Jenkins Priority: Major Reporter: Jason Davis
[JIRA] [perforce] (JENKINS-12202) Poll Exclude File(s) option doesn't handle build parameters
Jason Davis updated JENKINS-12202 Poll Exclude File(s) option doesnt handle build parameters Change By: Jason Davis (17/Apr/13 12:41 PM) Environment: Jenkins:1.511, Perforce plugin ServerVersion:2012. 1 ,Java1 . 36 7.0_17 , Jenkins PerforcePlugin: 1. 439 3.21,WindowsServer2008R2 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] [perforce] (JENKINS-12202) Poll Exclude File(s) option doesn't handle build parameters
Jason Davis updated JENKINS-12202 Poll Exclude File(s) option doesnt handle build parameters Change By: Jason Davis (17/Apr/13 12:42 PM) Environment: Jenkins:1.511, Perforce ServerVersion:2012. plugin 1 ,Java1 . 7.0_17 36 , PerforcePlugin: Jenkins 1. 3.21,WindowsServer2008R2 439 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.
