[JIRA] (JENKINS-61902) "authenticated" group doesn't work with Authorize Project plugin
Title: Message Title ikedam assigned an issue to akostadinov Groups that a user is assigned depends on the security realm you use. I suppose the security realm you use doesn't assign "authenticated" group to the user when authorize-project queries the user. I could not reproduce the issue with built-in "Jenkins’ own user database" as it always assigns "authenticated" group to the user. I don't think it's a bug of the security realm as the query by the authorize-project plugin is independent from user's login process. The security realm can't say to authorized-project plugin whether the user is authenticated. I suppose "authenticated" group is always assigned for Web UI operations as Jenkins knows the user is actually authenticated. I won't fix this issue as managing actual permissions is out of the domain of authorize-project and managing permissions carelessly can easily cause security issues. Please instead create a new group for all Jenkins users and assign the role to that group. Jenkins / JENKINS-61902 "authenticated" group doesn't work with Authorize Project plugin Change By: ikedam Assignee: ikedam akostadinov Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61902) "authenticated" group doesn't work with Authorize Project plugin
Title: Message Title ikedam updated an issue Jenkins / JENKINS-61902 "authenticated" group doesn't work with Authorize Project plugin Change By: ikedam Summary: Slave roles not respected "authenticated" group doesn't work with Authorize Project plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205774.1586890711000.13742.1587268560372%40Atlassian.JIRA.
[JIRA] (JENKINS-49135) Support for reusable sharing Declarative directives
Title: Message Title
Tavin Cole commented on JENKINS-49135
Re: Support for reusable sharing Declarative directives
Well if you want to mess around with Groovy AST, it does work to write something like this:
pipeline {
@MyAnnotation options
...
}
You can define @MyAnnotation just before calling the pipeline, e.g.:
@org.codehaus.groovy.transform.GroovyASTTransformationClass(['mypkg.MyTransformation'])
@interface MyAnnotation {}
MyTransformation will need to be in a global shared library, loaded automatically or with @Library. Then you have to replace the annotated statement with valid pipeline syntax. If the transformation is written in Groovy, it must be @NonCPS, and I've noticed that any errors don't seem to be logged – Jenkins just goes on and tries to execute the untransformed pipeline, which then fails syntax validation.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group
[JIRA] (JENKINS-61956) ItemGroupMixing#createProject() does not call Jenkins#checkGoodName
Title: Message Title Calvin Park commented on JENKINS-61956 Re: ItemGroupMixing#createProject() does not call Jenkins#checkGoodName and no insults please. I'm trying to improve Jenkins with my limited knowledge. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205840.1587161495000.13695.1587251820178%40Atlassian.JIRA.
[JIRA] (JENKINS-61956) ItemGroupMixing#createProject() does not call Jenkins#checkGoodName
Title: Message Title
Calvin Park commented on JENKINS-61956
Re: ItemGroupMixing#createProject() does not call Jenkins#checkGoodName
This is what I've got so far - far from a 5 line function. I'd appreciate your comments on how I can improve it
#jinja2: lstrip_blocks: True
#!/usr/bin/env groovy
import com.cloudbees.hudson.plugins.folder.Folder
import org.apache.commons.lang3.StringUtils;
// Create a folder in a parent folder
Folder create_folder(def parent_folder, String folder_name) {
// Actual create method call
parent_folder.createProject(Folder.class, folder_name)
// Below is unfortunately needed because createProject() doesn't return the
// newly created folder. Therefore need to query the full path again to fetch.
Jenkins jenkins = Jenkins.instance
String folder_path
if (parent_folder == jenkins) {
folder_path = folder_name
} else {
folder_path = parent_folder.fullName + "/" + folder_name
}
return jenkins.getItemByFullName(folder_path)
}
// Create a folder and its parent folders
Folder create_folder_recursively(String folder_path) {
// If the folder already exists, return
Folder jenkins_folder = Jenkins.instance.getItemByFullName(folder_path)
if (jenkins_folder)
return jenkins_folder
String folder_name, parent_path
def parent_folder
// If the folder is top level, set parent to Jenkins itself
if (!folder_path.contains("/")) {
parent_folder = Jenkins.instance
folder_name = folder_path
}
// If the folder is a sub-folder, recurse to create/fetch the parent folder
else {
folder_name = StringUtils.substringAfterLast(folder_path, "/")
parent_path = StringUtils.substringBeforeLast(folder_path, "/")
parent_folder = create_folder_recursively(parent_path)
}
// Create the folder in the parent folder
return create_folder(parent_folder, folder_name)
}
// Collect the names of all jobs and credentials
ArrayList names = new ArrayList();
{% for pipeline in pipelines %}
names.add("{{ pipeline.name }}")
{% endfor %}
{% for cred in credential_store %}
names.add("{{ cred.id }}")
{% endfor %}
// Filter to collect the names of all folders
ArrayList folders = new ArrayList();
for (String name : names) {
if (name.contains("/")) {
folders.add(StringUtils.substringBeforeLast(name, "/"))
}
}
// Remove duplicates
folders.unique().sort()
// Create folders and sub-folders
for (String folder_path : folders)
create_folder_recursively(folder_path)
Add Comment
[JIRA] (JENKINS-43821) Groovy AST Transformation class not called
Title: Message Title
Tavin Cole edited a comment on JENKINS-43821
Re: Groovy AST Transformation class not called
I made it work by writing a java class to implement {{ASTTransformation,}} and placing the compiled class file in the shared library {{src}} tree. It also works with a Groovy implementation, if the {{visit}} method is annotated {{@NonCPS}}. Without {{@NonCPS}} there is an error.No doubt, Pipeline has changed a lot since this bug was filed.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181339.1493124512000.13690.1587248700136%40Atlassian.JIRA.
[JIRA] (JENKINS-43821) Groovy AST Transformation class not called
Title: Message Title Tavin Cole commented on JENKINS-43821 Re: Groovy AST Transformation class not called I made it work by writing a java class to implement ASTTransformation, and placing the compiled class file in the shared library src tree. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181339.1493124512000.13686.1587247320163%40Atlassian.JIRA.
[JIRA] (JENKINS-61955) No valid crumb was included in the request
Title: Message Title Kevin Sheehan commented on JENKINS-61955 Re: No valid crumb was included in the request Will try 9.0.34 next week. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205838.1587157651000.13684.1587245700170%40Atlassian.JIRA.
[JIRA] (JENKINS-61872) Install Jenkins 2.222.1 on Windows Server 2016 (by Adminstrator user) error
Title: Message Title Robin Jansohn updated an issue Jenkins / JENKINS-61872 Install Jenkins 2.222.1 on Windows Server 2016 (by Adminstrator user) error This has nothing to do with the deploy-plugin. Moved it to core but I'm not sure this is an actual bug... Change By: Robin Jansohn Component/s: core Component/s: deploy-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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-61772) Multibranch pipeline cannot be disabled in GUI, only in config.xml
Title: Message Title Jaroslav Lhotak updated an issue Jenkins / JENKINS-61772 Multibranch pipeline cannot be disabled in GUI, only in config.xml Change By: Jaroslav Lhotak Labels: disabled multi-branch Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205610.1585773108000.13678.1587242340435%40Atlassian.JIRA.
[JIRA] (JENKINS-61772) Multibranch pipeline cannot be disabled in GUI, only in config.xml
Title: Message Title Jaroslav Lhotak commented on JENKINS-61772 Re: Multibranch pipeline cannot be disabled in GUI, only in config.xml Hello guys, do you have any estimate please? Thanks Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205610.1585773108000.13679.1587242340448%40Atlassian.JIRA.
[JIRA] (JENKINS-61955) No valid crumb was included in the request
Title: Message Title Daniel Beck resolved as Not A Defect Anyway, until this demonstrates that an issue in Jenkins caused the problem here, it looks more like a regression in Tomcat. Jenkins / JENKINS-61955 No valid crumb was included in the request Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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-61955) No valid crumb was included in the request
Title: Message Title Daniel Beck commented on JENKINS-61955 Re: No valid crumb was included in the request Have you tried newer releases of Tomcat? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205838.1587157651000.13672.1587241860153%40Atlassian.JIRA.
[JIRA] (JENKINS-61870) Git plugin UI transition for shallow clone needs more changes
Title: Message Title Mark Waite updated JENKINS-61870 Jenkins / JENKINS-61870 Git plugin UI transition for shallow clone needs more changes Change By: Mark Waite Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205735.1586539743000.13669.1587241560427%40Atlassian.JIRA.
[JIRA] (JENKINS-61871) Prune stale tags does not prune stale tags in my docker test
Title: Message Title Mark Waite updated JENKINS-61871 Jenkins / JENKINS-61871 Prune stale tags does not prune stale tags in my docker test Change By: Mark Waite Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205736.1586541813000.13666.1587241560362%40Atlassian.JIRA.
[JIRA] (JENKINS-61871) Prune stale tags does not prune stale tags in my docker test
Title: Message Title Mark Waite updated JENKINS-61871 Jenkins / JENKINS-61871 Prune stale tags does not prune stale tags in my docker test Change By: Mark Waite Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205736.1586541813000.13668.1587241560391%40Atlassian.JIRA.
[JIRA] (JENKINS-57720) Legacy pipeline library definition not supported by JCasC
Title: Message Title Mark Waite updated JENKINS-57720 Jenkins / JENKINS-57720 Legacy pipeline library definition not supported by JCasC Change By: Mark Waite Status: Fixed but Unreleased Closed Released As: configuration as code plugin 1.22 and later Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199663.1559067514000.13663.1587241320103%40Atlassian.JIRA.
[JIRA] (JENKINS-60489) beta forensics plugin reports no class def found for FilteredLog
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-60489 beta forensics plugin reports no class def found for FilteredLog Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203578.1576439299000.13662.1587241140393%40Atlassian.JIRA.
[JIRA] (JENKINS-60565) Null pointer exception in analysis beta plugin loading ResultAction
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-60565 Null pointer exception in analysis beta plugin loading ResultAction Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203674.1576889148000.13660.1587241140370%40Atlassian.JIRA.
[JIRA] (JENKINS-61932) "Learn more" link from new "Welcome" page is a broken redirect
Title: Message Title Mark Waite updated JENKINS-61932 Web site is updated and redirect works. Jenkins / JENKINS-61932 "Learn more" link from new "Welcome" page is a broken redirect Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205812.1587050215000.13657.1587241080335%40Atlassian.JIRA.
[JIRA] (JENKINS-61687) Exceptions due to race condition during build deletion
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-61687 Exceptions due to race condition during build deletion Change By: Daniel Beck Summary: Exceptions due to race condition during build deeltion deletion Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205510.1585173096000.13650.1587238980623%40Atlassian.JIRA.
[JIRA] (JENKINS-61958) failed to perform log rotation after a job
Title: Message Title Daniel Beck closed an issue as Duplicate Jenkins / JENKINS-61958 failed to perform log rotation after a job Change By: Daniel Beck Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205842.1587203635000.13652.1587238980757%40Atlassian.JIRA.
[JIRA] (JENKINS-61687) Exceptions due to race condition during build deeltion
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-61687 Exceptions due to race condition during build deeltion Change By: Daniel Beck Summary: Exceptions due to global race condition during build discarder deeltion Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205510.1585173096000.13636.1587238920592%40Atlassian.JIRA.
[JIRA] (JENKINS-61233) Do not activate the build discarder during version updates
Title: Message Title Daniel Beck closed an issue as Won't Fix As there have been no further reports of this behavior despite the feature having been in LTS for several weeks, I expect the issue that caused log deletion to be unrelated to global build discarders. Jenkins / JENKINS-61233 Do not activate the build discarder during version updates Change By: Daniel Beck Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe
[JIRA] (JENKINS-61956) createProject() and getItemsByFullName() handle nested folders inconsistently
Title: Message Title Daniel Beck commented on JENKINS-61956 Re: createProject() and getItemsByFullName() handle nested folders inconsistently It's like 5 lines of code to write a utility function. Don't be so lazy. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205840.1587161495000.13628.1587238740297%40Atlassian.JIRA.
[JIRA] (JENKINS-61956) ItemGroupMixing#createProject() does not call Jenkins#checkGoodName
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-61956 ItemGroupMixing#createProject() does not call Jenkins#checkGoodName Change By: Daniel Beck Summary: ItemGroupMixing# createProject() and getItemsByFullName() handle nested folders inconsistently does not call Jenkins#checkGoodName Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205840.1587161495000.13630.1587238740322%40Atlassian.JIRA.
[JIRA] (JENKINS-61955) No valid crumb was included in the request
Title: Message Title Kevin Sheehan commented on JENKINS-61955 Re: No valid crumb was included in the request added 9.0.30 har for same transaction Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205838.1587157651000.13624.1587231540224%40Atlassian.JIRA.
[JIRA] (JENKINS-61955) No valid crumb was included in the request
Title: Message Title Kevin Sheehan updated an issue Jenkins / JENKINS-61955 No valid crumb was included in the request Change By: Kevin Sheehan Attachment: 9.0.30.har Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205838.1587157651000.13623.1587231540213%40Atlassian.JIRA.
[JIRA] (JENKINS-61955) No valid crumb was included in the request
Title: Message Title Kevin Sheehan updated an issue Jenkins / JENKINS-61955 No valid crumb was included in the request Change By: Kevin Sheehan Environment: Jenkins 2.222.1Tomcat 9.0.31Windows Server 2012R2 JDK 1.8.0_241 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205838.1587157651000.13621.1587231000174%40Atlassian.JIRA.
[JIRA] (JENKINS-61955) No valid crumb was included in the request
Title: Message Title Kevin Sheehan commented on JENKINS-61955 Re: No valid crumb was included in the request Strict Crumb Issuer and Default Crumb Issues show the exact same behavior. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205838.1587157651000.13619.1587230640105%40Atlassian.JIRA.
[JIRA] (JENKINS-61955) No valid crumb was included in the request
Title: Message Title Kevin Sheehan commented on JENKINS-61955 Re: No valid crumb was included in the request Uploaded har file using 9.0.31 to simply save a job configuration and getting 403. Will revert to 9.0.30 and upload a har for the same transaction. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205838.1587157651000.13617.1587229920117%40Atlassian.JIRA.
[JIRA] (JENKINS-61955) No valid crumb was included in the request
Title: Message Title Kevin Sheehan updated an issue Jenkins / JENKINS-61955 No valid crumb was included in the request Change By: Kevin Sheehan Attachment: 9.0.31.har Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205838.1587157651000.13615.1587229800133%40Atlassian.JIRA.
[JIRA] (JENKINS-12848) Log parameters used for a build
Title: Message Title Pierre Beitz updated JENKINS-12848 Jenkins / JENKINS-12848 Log parameters used for a build Change By: Pierre Beitz Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.143306.1329845988000.13613.1587229620402%40Atlassian.JIRA.
[JIRA] (JENKINS-60336) Add support for logging to Elastic Search
Title: Message Title Pierre Beitz closed an issue as Fixed Jenkins / JENKINS-60336 Add support for logging to Elastic Search Change By: Pierre Beitz Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203348.1575231787000.13611.1587229620377%40Atlassian.JIRA.
[JIRA] (JENKINS-60336) Add support for logging to Elastic Search
Title: Message Title Pierre Beitz updated JENKINS-60336 Jenkins / JENKINS-60336 Add support for logging to Elastic Search Change By: Pierre Beitz Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203348.1575231787000.13609.1587229620349%40Atlassian.JIRA.
[JIRA] (JENKINS-60336) Add support for logging to Elastic Search
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-60336 Add support for logging to Elastic Search Change By: Pierre Beitz Labels: 3.5-fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203348.1575231787000.13605.1587229440207%40Atlassian.JIRA.
[JIRA] (JENKINS-12848) Log parameters used for a build
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-12848 Log parameters used for a build Change By: Pierre Beitz Labels: 3.5-fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.143306.1329845988000.13607.1587229440249%40Atlassian.JIRA.
[JIRA] (JENKINS-61963) Authenticate github pull requester and trigger the build as him/her
Title: Message Title Michael Who updated an issue Jenkins / JENKINS-61963 Authenticate github pull requester and trigger the build as him/her Change By: Michael Who * Trigger the build by pull request as an authenticated user. If github authentication is used, it could be the same as the pull requester Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205848.1587228599000.13603.1587228720171%40Atlassian.JIRA.
[JIRA] (JENKINS-60336) Add support for logging to Elastic Search
Title: Message Title Pierre Beitz updated JENKINS-60336 Jenkins / JENKINS-60336 Add support for logging to Elastic Search Change By: Pierre Beitz Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203348.1575231787000.13599.1587228600310%40Atlassian.JIRA.
[JIRA] (JENKINS-61963) Authenticate github pull requester and trigger the build as him/her
Title: Message Title Michael Who created an issue Jenkins / JENKINS-61963 Authenticate github pull requester and trigger the build as him/her Issue Type: New Feature Assignee: Kanstantsin Shautsou Components: github-integration-plugin, github-oauth-plugin Created: 2020-04-18 16:49 Priority: Minor Reporter: Michael Who Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received
[JIRA] (JENKINS-61955) No valid crumb was included in the request
Title: Message Title Kevin Sheehan commented on JENKINS-61955 Re: No valid crumb was included in the request Will put 9.0.31 back and check. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205838.1587157651000.13597.1587227400174%40Atlassian.JIRA.
[JIRA] (JENKINS-61500) workflow job (a) that calling another workflow job (b) - in Pipeline topology missing link from (a) to (b)
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-61500 workflow job (a) that calling another workflow job (b) - in Pipeline topology missing link from (a) to (b) Change By: Radi Berkovich Labels: 6.1.4-BETA Octane Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205187.1584435036000.13591.1587227100312%40Atlassian.JIRA.
[JIRA] (JENKINS-61362) avoid using of library "org.apache.commons.lang3." as it might not be on customer environment
Title: Message Title Radi Berkovich updated JENKINS-61362 Jenkins / JENKINS-61362 avoid using of library "org.apache.commons.lang3." as it might not be on customer environment Change By: Radi Berkovich Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205014.1583488696000.13595.1587227100408%40Atlassian.JIRA.
[JIRA] (JENKINS-61500) workflow job (a) that calling another workflow job (b) - in Pipeline topology missing link from (a) to (b)
Title: Message Title Radi Berkovich updated JENKINS-61500 Jenkins / JENKINS-61500 workflow job (a) that calling another workflow job (b) - in Pipeline topology missing link from (a) to (b) Change By: Radi Berkovich Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205187.1584435036000.13592.1587227100363%40Atlassian.JIRA.
[JIRA] (JENKINS-61500) workflow job (a) that calling another workflow job (b) - in Pipeline topology missing link from (a) to (b)
Title: Message Title Radi Berkovich updated JENKINS-61500 Jenkins / JENKINS-61500 workflow job (a) that calling another workflow job (b) - in Pipeline topology missing link from (a) to (b) Change By: Radi Berkovich Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205187.1584435036000.13593.1587227100378%40Atlassian.JIRA.
[JIRA] (JENKINS-61362) avoid using of library "org.apache.commons.lang3." as it might not be on customer environment
Title: Message Title Radi Berkovich updated JENKINS-61362 Jenkins / JENKINS-61362 avoid using of library "org.apache.commons.lang3." as it might not be on customer environment Change By: Radi Berkovich Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205014.1583488696000.13594.1587227100393%40Atlassian.JIRA.
[JIRA] (JENKINS-60670) StackOverflowError due to the HP ALM implementation of GraphListener
Title: Message Title Radi Berkovich updated JENKINS-60670 Jenkins / JENKINS-60670 StackOverflowError due to the HP ALM implementation of GraphListener Change By: Radi Berkovich Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203913.1578384494000.13590.1587227040476%40Atlassian.JIRA.
[JIRA] (JENKINS-61833) On "test connection" to ALM Octane - show available ALM Octane workspaces
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-61833 On "test connection" to ALM Octane - show available ALM Octane workspaces Change By: Radi Berkovich Labels: 6.2.1-BETA Octane Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205686.1586269018000.13586.1587227040427%40Atlassian.JIRA.
[JIRA] (JENKINS-61832) Allow to disable ALM Octane configuration temporary
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-61832 Allow to disable ALM Octane configuration temporary Change By: Radi Berkovich Labels: 6.2.1-BETA Octane Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205685.1586268739000.13585.1587227040379%40Atlassian.JIRA.
[JIRA] (JENKINS-60670) StackOverflowError due to the HP ALM implementation of GraphListener
Title: Message Title Radi Berkovich updated JENKINS-60670 Jenkins / JENKINS-60670 StackOverflowError due to the HP ALM implementation of GraphListener Change By: Radi Berkovich Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203913.1578384494000.13588.1587227040451%40Atlassian.JIRA.
[JIRA] (JENKINS-61962) Remove UFT auto-generated job cleaner
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-61962 Remove UFT auto-generated job cleaner Change By: Radi Berkovich Labels: 6.2.1-BETA Octane Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205847.1587226698000.13584.1587226980058%40Atlassian.JIRA.
[JIRA] (JENKINS-60640) Support rename and move job and sync it in pipeline module in ALM Octane
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-60640 Support rename and move job and sync it in pipeline module in ALM Octane Change By: Radi Berkovich Labels: 6 6 .0.4-BETA 6.2.1-BETA Octane Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203878.1578238949000.13583.1587226860378%40Atlassian.JIRA.
[JIRA] (JENKINS-60640) Support rename and move job and sync it in pipeline module in ALM Octane
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-60640 Support rename and move job and sync it in pipeline module in ALM Octane Change By: Radi Berkovich Labels: 6 6 .0.4-BETA Octane Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203878.1578238949000.13582.1587226860366%40Atlassian.JIRA.
[JIRA] (JENKINS-60640) Support rename job and sync it in pipeline module in ALM Octane
Title: Message Title Radi Berkovich reopened an issue Jenkins / JENKINS-60640 Support rename job and sync it in pipeline module in ALM Octane Change By: Radi Berkovich Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203878.1578238949000.13580.1587226860324%40Atlassian.JIRA.
[JIRA] (JENKINS-60640) Support rename and move job and sync it in pipeline module in ALM Octane
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-60640 Support rename and move job and sync it in pipeline module in ALM Octane Change By: Radi Berkovich Summary: Support rename and move job and sync it in pipeline module in ALM Octane Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203878.1578238949000.13581.1587226860354%40Atlassian.JIRA.
[JIRA] (JENKINS-61962) Remove UFT auto-generated job cleaner
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-61962 Remove UFT auto-generated job cleaner Issue Type: New Feature Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2020-04-18 16:18 Priority: Minor Reporter: Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed
[JIRA] (JENKINS-61961) Jenkins Migration - Credentials not auto-populate in jobs.
Title: Message Title Anuj Gupta created an issue Jenkins / JENKINS-61961 Jenkins Migration - Credentials not auto-populate in jobs. Issue Type: Improvement Assignee: Thomas Fürer Attachments: Jenkins-Issue.PNG Components: thinbackup-plugin Created: 2020-04-18 16:13 Priority: Major Reporter: Anuj Gupta Hi, I am migrating jenkins from server A to server B. I copied all configuration from /home/jenkins/.jenkins including config.xml, workspace, credentials.xml etc. After migration, I can see all jobs on Jenkins dashboard but I need to select the credentials which I am using on server A e.g. Github authentication credentials. I can see those credentials in drop-down menu but need to select for each job. This is taking a lot of time. Is there any workaround or any option that those credentials automatically got hold on dashboard of Server B Jenkins ? Thanks Anuj Add Comment
[JIRA] (JENKINS-61949) Configuration of action triggers in an Organization folder
Title: Message Title Aytunc BEKEN commented on JENKINS-61949 Re: Configuration of action triggers in an Organization folder Hi, Thanks for the feedback, As I understand there are three different topics. Let me summarize and ask some more questions to get some details. 1- GitHub Organization Folder: Organization folders was implemented, I need to check 2- Individual Configuration for Triggers Jobs in MultiBranch Jobs which are created by Organizational Folder: I am not sure how this works but I will check. 3- Could you please give some example about "programmatically" ? 4- "Or if not possible, maybe allow running against a branch of the repository that triggered the action?": I thought this before, this can create race condition between the plugin and multibranch plugin. For example, Trigger Job start when a new branch is discovered, If the branch job, which is also set as trigger job, is not indexed yet other branch jobs will fail. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205829.1587131764000.13573.1587224880255%40Atlassian.JIRA.
[JIRA] (JENKINS-61949) Configuration of action triggers in an Organization folder
Title: Message Title Aytunc BEKEN edited a comment on JENKINS-61949 Re: Configuration of action triggers in an Organization folder Hi, Thanks for the feedback, As I understand there are three four different topics. Let me summarize and ask some more questions to get some details.1- GitHub Organization Folder: Organization folders was implemented, I need to check2- Individual Configuration for Triggers Jobs in MultiBranch Jobs which are created by Organizational Folder: I am not sure how this works but I will check.3- Could you please give some example about "programmatically" ? 4- "Or if not possible, maybe allow running against a branch of the repository that triggered the action?": I thought this before, this can create race condition between the plugin and multibranch plugin. For example, Trigger Job start when a new branch is discovered, If the branch job, which is also set as trigger job, is not indexed yet other branch jobs will fail. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205829.1587131764000.13576.1587224880295%40Atlassian.JIRA.
[JIRA] (JENKINS-61942) Can this be configured to use bitbucket server
Title: Message Title Aytunc BEKEN commented on JENKINS-61942 Re: Can this be configured to use bitbucket server Hi, There is no restriction. Could you please share screenshot ? I need to understand well. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205822.1587082749000.13570.1587224460387%40Atlassian.JIRA.
[JIRA] (JENKINS-61941) bitbucket server
Title: Message Title Aytunc BEKEN commented on JENKINS-61941 Re: bitbucket server Duplicate JENKINS-61942 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205821.1587082567000.13559.1587224400748%40Atlassian.JIRA.
[JIRA] (JENKINS-61941) bitbucket server
Title: Message Title Aytunc BEKEN closed an issue as Duplicate Jenkins / JENKINS-61941 bitbucket server Change By: Aytunc BEKEN Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205821.1587082567000.13564.1587224400972%40Atlassian.JIRA.
[JIRA] (JENKINS-38220) Support for EC2 instance profile credentials
Title: Message Title Oleksandr Shmyrko updated an issue Jenkins / JENKINS-38220 Support for EC2 instance profile credentials Change By: Oleksandr Shmyrko Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174381.1473894967000.13549.1587215280643%40Atlassian.JIRA.
[JIRA] (JENKINS-26336) Compact Columns Plugin does not play well with Folders Plugin
Title: Message Title Tobias Gruetzmacher updated JENKINS-26336 Jenkins / JENKINS-26336 Compact Columns Plugin does not play well with Folders Plugin Change By: Tobias Gruetzmacher Status: Open Fixed but Unreleased Assignee: Jacob Robertson Tobias Gruetzmacher Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159998.1420713364000.13545.1587213600452%40Atlassian.JIRA.
[JIRA] (JENKINS-12848) Log parameters used for a build
Title: Message Title Pierre Beitz updated JENKINS-12848 Jenkins / JENKINS-12848 Log parameters used for a build Change By: Pierre Beitz Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.143306.1329845988000.13542.1587212640215%40Atlassian.JIRA.
[JIRA] (JENKINS-61919) Audit trail plugin shows anonymous user logged out
Title: Message Title Pierre Beitz commented on JENKINS-61919 Re: Audit trail plugin shows anonymous user logged out Ankur Could you please share: a sample of the entry you see the pattern you use Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205793.1586970989000.13540.1587212160133%40Atlassian.JIRA.
[JIRA] (JENKINS-61960) Migrate the shelve project documentation
Title: Message Title Pierre Beitz started work on JENKINS-61960 Change By: Pierre Beitz Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205844.1587211241000.13537.1587211800170%40Atlassian.JIRA.
[JIRA] (JENKINS-61960) Migrate the shelve project documentation
Title: Message Title Pierre Beitz updated JENKINS-61960 Jenkins / JENKINS-61960 Migrate the shelve project documentation Change By: Pierre Beitz Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205844.1587211241000.13538.1587211800218%40Atlassian.JIRA.
[JIRA] (JENKINS-61960) Migrate the shelve project documentation
Title: Message Title Pierre Beitz created an issue Jenkins / JENKINS-61960 Migrate the shelve project documentation Issue Type: Task Assignee: Pierre Beitz Components: shelve-project-plugin Created: 2020-04-18 12:00 Priority: Minor Reporter: Pierre Beitz Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-61854) "Test Ldap Settings" button stopped functioning.
Title: Message Title
William Gillaspy edited a comment on JENKINS-61854
Re: "Test Ldap Settings" button stopped functioning.
Thanks Baptiste.Button and form is functional. Testing with the same user/password that I'm already logged in as results in:!image-2020-04-18-07-06-52-382.png|width=784,height=154!Looking for that id in the l og log :{code:java}Apr 18, 2020 7:04:03 AM WARNING hudson.init.impl.InstallUncaughtExceptionHandler handleExceptionCaught unhandled exception with ID 7a959e7f-f9aa-4909-a7ed-aae6384e4054net.sf.json.JSONException: null object at net.sf.json.JSONObject.verifyIsNull(JSONObject.java:2688) at net.sf.json.JSONObject.getJSONObject(JSONObject.java:1998) at hudson.security.LDAPSecurityRealm$DescriptorImpl.doValidate(LDAPSecurityRealm.java:1629) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at com.splunk.splunkjenkins.WebPostAccessLogger.doFilter(WebPostAccessLogger.java:39) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:248) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:239) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:215) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:88) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:114) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at
[JIRA] (JENKINS-61854) "Test Ldap Settings" button stopped functioning.
Title: Message Title William Gillaspy commented on JENKINS-61854 Re: "Test Ldap Settings" button stopped functioning. Thanks Baptiste. Button and form is functional. Testing with the same user/password that I'm already logged in as results in: Looking for that id in the l og: Apr 18, 2020 7:04:03 AM WARNING hudson.init.impl.InstallUncaughtExceptionHandler handleExceptionCaught unhandled exception with ID 7a959e7f-f9aa-4909-a7ed-aae6384e4054 net.sf.json.JSONException: null object at net.sf.json.JSONObject.verifyIsNull(JSONObject.java:2688) at net.sf.json.JSONObject.getJSONObject(JSONObject.java:1998) at hudson.security.LDAPSecurityRealm$DescriptorImpl.doValidate(LDAPSecurityRealm.java:1629) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at com.splunk.splunkjenkins.WebPostAccessLogger.doFilter(WebPostAccessLogger.java:39) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:248) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:239) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:215) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:88) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:114) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at
[JIRA] (JENKINS-61854) "Test Ldap Settings" button stopped functioning.
Title: Message Title William Gillaspy updated an issue Jenkins / JENKINS-61854 "Test Ldap Settings" button stopped functioning. Change By: William Gillaspy Attachment: image-2020-04-18-07-06-52-382.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205717.1586439894000.13517.1587208020549%40Atlassian.JIRA.
[JIRA] (JENKINS-61959) CpsThread(Timeout) raises InterruptedException
Title: Message Title
Thomas Ullrich updated an issue
Jenkins / JENKINS-61959
CpsThread(Timeout) raises InterruptedException
Change By:
Thomas Ullrich
Our declarative pipeline(for isolating the problem) is using a custom step of our shared library. This custom step shall represent a long running REST call by just calling Thread.sleep (36).Code: {{pipeline\{agent{label'master'}options\{ timestamps() buildDiscarder(logRotator(numToKeepStr: '10'))skipDefaultCheckout()}stages\{ stage('Thread.sleep'){steps{sleepService(36)}}Custom step from shared library: {{import java.lang.*;def String call(long millis) \{timeout(600){echo "Current thread name: ${Thread.currentThread().getName()}"echo "Current thread classname: ${Thread.currentThread().getClass().getName()}"Thread.sleep (millis)Executing this, is causing the following exception: {{java.lang.InterruptedException: sleep interruptedat java.lang.Thread.sleep(Native Method)at java_lang_Thread$sleep.call(Unknown Source)at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20)at soiServiceSleep.call(soiServiceSleep.groovy:9)at ___cps.transform___(Native Method)at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:86)at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:113)at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:83)at sun.reflect.GeneratedMethodAccessor577.invoke(Unknown Source)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:498)at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)at com.cloudbees.groovy.cps.impl.LocalVariableBlock$LocalVariable.get(LocalVariableBlock.java:39)at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)at com.cloudbees.groovy.cps.impl.LocalVariableBlock.evalLValue(LocalVariableBlock.java:28)at com.cloudbees.groovy.cps.LValueBlock$BlockImpl.eval(LValueBlock.java:55)at com.cloudbees.groovy.cps.LValueBlock.eval(LValueBlock.java:16)at com.cloudbees.groovy.cps.Next.step(Next.java:83)at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174)at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:129)at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:268)at
[JIRA] (JENKINS-61959) CpsThread(Timeout) raises InterruptedException
Title: Message Title Thomas Ullrich created an issue Jenkins / JENKINS-61959 CpsThread(Timeout) raises InterruptedException Issue Type: Bug Assignee: Unassigned Components: workflow-cps-plugin Created: 2020-04-18 10:25 Environment: Jenkins ver. 2.190.1 workflow CPS plugin ver. 2.80 Priority: Major Reporter: Thomas Ullrich Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-56087) Chanel name case sensitive error ignored
Title: Message Title
Lionel FÉLICITÉ edited a comment on JENKINS-56087
Re: Chanel name case sensitive error ignored
Hi, I tottally forgot to test with 1.4.3. Ijust tested with 1. 48 4.8 & jenkins 2.228. I created a new chan "Test_Lionel" * On the first run of "test connection" ** nothing was written on this chan ** I got this stack ** {quote}2020-04-18 10:04:10.161+ [id=240] SEVERE j.p.r.r.RocketChatClientImpl#sendSingleMessage: Could not send message: Response \ {success=false, messages=null, message=null, users=null, user=null, channels=null, channel=null, version=null, error=[invalid-channel]}2020-04-18 10:04:10.162+ [id=240] SEVERE j.p.r.RocketClientImpl#publish: I/O error error during publishing messagejenkins.plugins.rocketchatnotifier.rocket.errorhandling.RocketClientException: The send of the message was unsuccessful. Response \ {success=false, messages=null, message=null, users=null, user=null, channels=null, channel=null, version=null, error=[invalid-channel]} at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientImpl.sendSingleMessage(RocketChatClientImpl.java:183) at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientImpl.send(RocketChatClientImpl.java:148) at jenkins.plugins.rocketchatnotifier.RocketClientImpl.publish(RocketClientImpl.java:37) at jenkins.plugins.rocketchatnotifier.RocketChatNotifier$DescriptorImpl.doTestConnection(RocketChatNotifier.java:625) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154)2020-04-18 10:04:10.161+ [id=240] SEVERE j.p.r.r.RocketChatClientImpl#sendSingleMessage: Could not send message: Response \ {success=false, messages=null, message=null, users=null, user=null, channels=null, channel=null, version=null, error=[invalid-channel]}2020-04-18 10:04:10.162+ [id=240] SEVERE j.p.r.RocketClientImpl#publish: I/O error error during publishing messagejenkins.plugins.rocketchatnotifier.rocket.errorhandling.RocketClientException: The send of the message was unsuccessful. Response \ {success=false, messages=null, message=null, users=null, user=null, channels=null, channel=null, version=null, error=[invalid-channel]} at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientImpl.sendSingleMessage(RocketChatClientImpl.java:183) at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientImpl.send(RocketChatClientImpl.java:148) at jenkins.plugins.rocketchatnotifier.RocketClientImpl.publish(RocketClientImpl.java:37) at
[JIRA] (JENKINS-56087) Chanel name case sensitive error ignored
Title: Message Title
Lionel FÉLICITÉ commented on JENKINS-56087
Re: Chanel name case sensitive error ignored
Hi, I tottally forgot to test with 1.4.3. Ijust tested with 1.48 & jenkins 2.228. I created a new chan "Test_Lionel"
On the first run of "test connection"
nothing was written on this chan
I got this stack
2020-04-18 10:04:10.161+ [id=240] SEVERE j.p.r.r.RocketChatClientImpl#sendSingleMessage: Could not send message: Response{success=false, messages=null, message=null, users=null, user=null, channels=null, channel=null, version=null, error=[invalid-channel]} 2020-04-18 10:04:10.162+ [id=240] SEVERE j.p.r.RocketClientImpl#publish: I/O error error during publishing message jenkins.plugins.rocketchatnotifier.rocket.errorhandling.RocketClientException: The send of the message was unsuccessful. Response{success=false, messages=null, message=null, users=null, user=null, channels=null, channel=null, version=null, error=[invalid-channel]} at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientImpl.sendSingleMessage(RocketChatClientImpl.java:183) at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientImpl.send(RocketChatClientImpl.java:148) at jenkins.plugins.rocketchatnotifier.RocketClientImpl.publish(RocketClientImpl.java:37) at jenkins.plugins.rocketchatnotifier.RocketChatNotifier$DescriptorImpl.doTestConnection(RocketChatNotifier.java:625) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154)2020-04-18 10:04:10.161+ [id=240] SEVERE j.p.r.r.RocketChatClientImpl#sendSingleMessage: Could not send message: Response{success=false, messages=null, message=null, users=null, user=null, channels=null, channel=null, version=null, error=[invalid-channel]} 2020-04-18 10:04:10.162+ [id=240] SEVERE j.p.r.RocketClientImpl#publish: I/O error error during publishing message
[JIRA] (JENKINS-56087) Chanel name case sensitive error ignored
Title: Message Title Lionel FÉLICITÉ assigned an issue to Martin Reinhardt Jenkins / JENKINS-56087 Chanel name case sensitive error ignored Change By: Lionel FÉLICITÉ Assignee: Lionel FÉLICITÉ Martin Reinhardt Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197516.1549893316000.13511.1587204660334%40Atlassian.JIRA.
[JIRA] (JENKINS-61958) failed to perform log rotation after a job
Title: Message Title
Lionel FÉLICITÉ updated an issue
Jenkins / JENKINS-61958
failed to perform log rotation after a job
Change By:
Lionel FÉLICITÉ
On running a simple job (running on jenkins master), I got{quote}2020-04-18 09:33:29.132+ [id=207] INFO o.j.p.workflow.job.WorkflowRun#finish: project #50 completed: SUCCESS2020-04-18 09:33:30.711+ [id=40] WARNING o.j.p.workflow.job.WorkflowRun#lambda$finish$2: failed to perform log rotation after project #50Also: java.nio.file.NoSuchFileException: /data/jenkins/jobs/project/builds/40 -> /data/jenkins/jobs/project/builds/.40 at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:396) at sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262) at java.nio.file.Files.move(Files.java:1395) at hudson.model.Run.delete(Run.java:1645) at hudson.tasks.LogRotator.perform(LogRotator.java:166)jenkins.util.io.CompositeIOException: Failed to rotate logs for [project #40 |#40 ] at hudson.tasks.LogRotator.perform(LogRotator.java:223) at hudson.model.Job.logRotate(Job.java:469) at org.jenkinsci.plugins.workflow.job.WorkflowRun.lambda$finish$2(WorkflowRun.java:612) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){quote} I ran it a second time:{quote}2020-04-18 09:35:48.652+ [id=467] INFO o.j.p.workflow.job.WorkflowRun#finish: project #51 completed: SUCCESS2020-04-18 09:35:48.962+ [id=42] WARNING o.j.p.workflow.job.WorkflowRun#lambda$finish$2: failed to perform log rotation after project #51Also: java.nio.file.NoSuchFileException: /data/jenkins/jobs/project/builds/41 -> /data/jenkins/jobs/project/builds/.41 at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:396) at sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262) at java.nio.file.Files.move(Files.java:1395) at hudson.model.Run.delete(Run.java:1645) at hudson.tasks.LogRotator.perform(LogRotator.java:166)jenkins.util.io.CompositeIOException: Failed to rotate logs for [project #41 |#41 ] at hudson.tasks.LogRotator.perform(LogRotator.java:223) at hudson.model.Job.logRotate(Job.java:469) at
[JIRA] (JENKINS-61958) failed to perform log rotation after a job
Title: Message Title Lionel FÉLICITÉ created an issue Jenkins / JENKINS-61958 failed to perform log rotation after a job Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-04-18 09:53 Environment: OS: debian 8 java: openjdk version "1.8.0_171" OpenJDK Runtime Environment (build 1.8.0_171-8u171-b11-1~bpo8+1-b11) OpenJDK 64-Bit Server VM (build 25.171-b11, mixed mode) Jenkins version: 2.228 (via jenkins weekly repo) Firefox 68.7.0 esr Priority: Minor Reporter: Lionel FÉLICITÉ On running a simple job (running on jenkins master), I got 2020-04-18 09:33:29.132+ [id=207] INFO o.j.p.workflow.job.WorkflowRun#finish: project #50 completed: SUCCESS 2020-04-18 09:33:30.711+ [id=40] WARNING o.j.p.workflow.job.WorkflowRun#lambda$finish$2: failed to perform log rotation after project #50 Also: java.nio.file.NoSuchFileException: /data/jenkins/jobs/project/builds/40 -> /data/jenkins/jobs/project/builds/.40 at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:396) at sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262) at java.nio.file.Files.move(Files.java:1395) at hudson.model.Run.delete(Run.java:1645) at hudson.tasks.LogRotator.perform(LogRotator.java:166) jenkins.util.io.CompositeIOException: Failed to rotate logs for project #40 at hudson.tasks.LogRotator.perform(LogRotator.java:223) at hudson.model.Job.logRotate(Job.java:469) at org.jenkinsci.plugins.workflow.job.WorkflowRun.lambda$finish$2(WorkflowRun.java:612) at
[JIRA] (JENKINS-61957) Azure Function APP is listing under Webapp in Jenkins Pulish to Webapp
Title: Message Title sridevi Kunnath updated an issue Jenkins / JENKINS-61957 Azure Function APP is listing under Webapp in Jenkins Pulish to Webapp Change By: sridevi Kunnath While trying to build azure function app through jenkins , we are not able to list the functions app instead function app is getting listed under webapp section, Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205841.1587193819000.13505.1587193920141%40Atlassian.JIRA.
[JIRA] (JENKINS-61957) Azure Function APP is listing under Webapp in Jenkins Pulish to Webapp
Title: Message Title sridevi Kunnath created an issue Jenkins / JENKINS-61957 Azure Function APP is listing under Webapp in Jenkins Pulish to Webapp Issue Type: Bug Assignee: Azure DevOps Components: azure-app-service-plugin Created: 2020-04-18 07:10 Environment: Dev Priority: Major Reporter: sridevi Kunnath While trying to build azure function app, we are not able to list the functions app instead function app is getting listed under webapp section, Add Comment
