When using the Build Symlink Plugin of version 1.1 in our Jenkins (Version 2.361.4 with Java 11.0.16.1) the build links for the successful builds are not being updated properly. As for our downstream jobs we will be fetching the lastSuccessful artifacts from upstream build this is causing a severe issue. Able to notice that 'permalinks' are updated properly, but softlinks are not proper and is causing problems for us.
I have tried the below methods to fix the issue, but none worked:
reinstalled the plugin itself and restarting Jenkins.
Enabling and disabling of the plugin in Plugin Manager.
Deleting the last* soft links manually in server and rebuilding is updating the links properly but this solution is not feasible as we have large number of jobs.
As in Jenkins official page not able to see other supported plugins to upgrade or downgrade, we are stuck with this version 1.1
Attached images of permalinks and softlinks for reference where the latest successful build is 187. Please support on how we can procced to fix this issue. Any suggestions and alternatives will also be appreciated.
Thank you for your response, Could you please further support on below query. I am not able to find the option 'io.jenkins.plugins.build_symlink' here. Should i go with 'io.jenkins.plugins.build_symlink.RunListenerImpl' and proceed with FINE level?
Parinith
added a comment - - edited Hello Jesse,
Thank you for your response, Could you please further support on below query. I am not able to find the option 'io.jenkins.plugins.build_symlink' here. Should i go with 'io.jenkins.plugins.build_symlink.RunListenerImpl' and proceed with FINE level?
Not sure. From the log it looks like it is the text file permalinks which is not getting updated: PeepholePermalink.resolve is returning 16174.
Jesse Glick
added a comment - Not sure. From the log it looks like it is the text file permalinks which is not getting updated: PeepholePermalink.resolve is returning 16174.
In this scenario the permalinks are updated properly with 977 build number, but in logs shows no change with still pointing to 976 build.
Parinith
added a comment - - edited In this scenario the permalinks are updated properly with 977 build number, but in logs shows no change with still pointing to 976 build.
Perhaps someone will find the following script useful to find discrepancies of the build numbers between permalinks and the symbolic links.
The script finds all files with the name permalinks recursively in a given directory and compares the build number of the specified link with the associated build number in permalinks. If the numbers do not match, the path to this job is printed.
Usage example: check_permalinks.sh jenkins/home/builds lastCompletedBuild
parinith_135 not sure what is going on. Check whether the log messages are coming after the completion of the last successful build. A pull request would be welcome if you figure it out.
Jesse Glick
added a comment - parinith_135 not sure what is going on. Check whether the log messages are coming after the completion of the last successful build. A pull request would be welcome if you figure it out.
If someone is able to reproduce the problem from scratch, a pull request would be appreciated (and maybe you can adopt the plugin).
Jesse Glick
added a comment - If someone is able to reproduce the problem from scratch, a pull request would be appreciated (and maybe you can adopt the plugin).
Hello Jesse Glick, we are still seeing the same issues. Do you have any alternative way to fetch these lastSuccessful, lastFailed, lastStable etc data for the builds in a job? Please let us know for any workaround also
Parinith
added a comment - Hello Jesse Glick, we are still seeing the same issues. Do you have any alternative way to fetch these lastSuccessful, lastFailed, lastStable etc data for the builds in a job? Please let us know for any workaround also
Unassigned
Parinith
Votes:
0Vote for this issue
Watchers:
4Start watching this issue
Created:
Updated:
{"errorMessages":["jqlTooComplex"],"errors":{}}
[{"id":-1,"name":"My open issues","jql":"assignee = currentUser() AND resolution = Unresolved order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-2,"name":"Reported by me","jql":"reporter = currentUser() order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-4,"name":"All issues","jql":"order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-5,"name":"Open issues","jql":"resolution = Unresolved order by priority DESC,updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-9,"name":"Done issues","jql":"statusCategory = Done order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-3,"name":"Viewed recently","jql":"issuekey in issueHistory() order by lastViewed DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-6,"name":"Created recently","jql":"created >= -1w order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-7,"name":"Resolved recently","jql":"resolutiondate >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-8,"name":"Updated recently","jql":"updated >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false}]
Hello Jesse,
Thank you for your response, Could you please further support on below query. I am not able to find the option 'io.jenkins.plugins.build_symlink' here. Should i go with 'io.jenkins.plugins.build_symlink.RunListenerImpl' and proceed with FINE level?