[JIRA] (JENKINS-60632) git plugin no longer clones repositories with backslashes
Title: Message Title Michael DeGuzis commented on JENKINS-60632 Re: git plugin no longer clones repositories with backslashes Mark once these two PRs are done, will you need to update your plugin to use the new executable/binary? https://github.com/git-for-windows/git/pull/2437 https://github.com/git/git/pull/682 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203868.1578058546000.2022.1578064440155%40Atlassian.JIRA.
[JIRA] (JENKINS-60632) git plugin no longer clones repositories with backslashes
Title: Message Title Michael DeGuzis edited a comment on JENKINS-60632 Re: git plugin no longer clones repositories with backslashes Ok, at least it's good confirmation for others to note this as being out of your control. Now that the issue is logged and with references, it could be closed and others cna track the git for windows issue. It's unfortunate I cannot implement the workaround with this plugin, effectively leaving me stranded. Is it not possible to modify the GitSCM class parameters (much like I do already for submodule handling) to implement the workaround? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203868.1578058546000.2020.1578064200214%40Atlassian.JIRA.
[JIRA] (JENKINS-60632) git plugin no longer clones repositories with backslashes
Title: Message Title Michael DeGuzis commented on JENKINS-60632 Re: git plugin no longer clones repositories with backslashes Ok, at least it's good confirmation for others to note this as being out of your control. Now that the issue is logged and with references, it could be closed and others cna track the git for windows issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203868.1578058546000.2018.1578063900181%40Atlassian.JIRA.
[JIRA] (JENKINS-60632) git plugin no longer clones repositories with backslashes
Title: Message Title
Michael DeGuzis updated an issue
Jenkins / JENKINS-60632
git plugin no longer clones repositories with backslashes
Change By:
Michael DeGuzis
https://plugins.jenkins.io/gitVersion 4.0.0.0While I no longer have any file (since 2017) in my files on any branch, the git tree is being picked up and killing interfering with the clone so that Jenkins throws an incorrect exit code .{code}$ rm -rf python-mypkg && git clone https://github.com/org/mypkgCloning into 'python-mypkg'...remote: Enumerating objects: 3, done.remote: Counting objects: 100% (3/3), done.remote: Compressing objects: 100% (2/2), done.error: filename in tree entry contains backslash: '\'remote: Total 7683 (delta 0), reused 2 (delta 0), pack-reused 7680Receiving objects: 100% (7683/7683), 1.34 MiB | 5.39 MiB/s, done.error: filename in tree entry contains backslash: '\'error: filename in tree entry contains backslash: '\'Resolving deltas: 100% (5011/5011), done.{code} Jenkins:{code}Cloning the remote Git repository > git config core.sparsecheckout # timeout=10 > git checkout -f 1bcc1100ab4624b864b3e8072cb8f171a6d08d77 # timeout=10Cloning repository https://github.com/org/mypkg > git init C:\Jenkins\workspace\operations\job\mypkh # timeout=10Fetching upstream changes from https://github.com/GeisingerHealthSystem/python-udaopstools > git --version # timeout=10using GIT_ASKPASS to set credentials Ops team machine account > git fetch --tags --force --progress -- https://github.com/org/mypk +refs/heads/ * :refs/remotes/origin/* # timeout=10ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "git fetch --tags --force --progress -- https://github.com/org/mypkg +refs/heads/*:refs/remotes/origin/*" returned status code 1:stdout: stderr: remote: Enumerating objects: 3, done.remote: Counting objects: 33% (1/3)remote: Counting objects: 66% (2/3)remote: Counting objects: 100% (3/3)remote: Counting objects: 100% (3/3), done.remote: Compressing objects: 50% (1/2)remote: Compressing objects: 100% (2/2)remote: Compressing objects: 100% (2/2), done.Receiving objects: 0% (1/7683)Receiving objects: 1% (77/7683)Receiving objects: 2% (154/7683)Receiving objects: 3% (231/7683)Receiving objects: 4% (308/7683)Receiving objects: 5% (385/7683)Receiving objects: 6% (461/7683)Receiving objects: 7% (538/7683)Receiving objects: 8% (615/7683)Receiving objects: 9% (692/7683)Receiving objects: 10% (769/7683)Receiving objects: 11% (846/7683)Receiving objects: 12% (922/7683)Receiving objects: 13% (999/7683)Receiving objects: 14% (1076/7683)Receiving objects: 15% (1153/7683)Receiving objects: 16% (1230/7683)Receiving objects: 17% (1307/7683)Receiving objects: 18% (1383/7683)Receiving objects: 19% (1460/7683)Receiving objects: 20% (1537/7683)Receiving objects: 21% (1614/7683)Receiving objects: 22% (1691/7683)Receiving objects: 23% (1768/7683)Receiving objects: 24% (1844/7683)Receiving objects: 25%
[JIRA] (JENKINS-60632) git plugin no longer clones repositories with backslashes
Title: Message Title Michael DeGuzis created an issue Jenkins / JENKINS-60632 git plugin no longer clones repositories with backslashes Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2020-01-03 13:35 Environment: Jenkins LTS 2.204.1 (Docker) Labels: git pipline Priority: Minor Reporter: Michael DeGuzis https://plugins.jenkins.io/git Version 4.0.0.0 While I no longer have any file (since 2017) in my files on any branch, the git tree is being picked up and killing the clone. $ rm -rf python-mypkg && git clone https://github.com/org/mypkg Cloning into 'python-mypkg'... remote: Enumerating objects: 3, done. remote: Counting objects: 100% (3/3), done. remote: Compressing objects: 100% (2/2), done. error: filename in tree entry contains backslash: '\' remote: Total 7683 (delta 0), reused 2 (delta 0), pack-reused 7680 Receiving objects: 100% (7683/7683), 1.34 MiB | 5.39 MiB/s, done. error: filename in tree entry contains backslash: '\' error: filename in tree entry contains backslash: '\' Resolving deltas: 100% (5011/5011), done. Related: https://github.com/git-for-windows/git/issues/2435
[JIRA] (JENKINS-60190) Parameter references clash with variables, regardless of case.
Title: Message Title
Michael DeGuzis updated an issue
Jenkins / JENKINS-60190
Parameter references clash with variables, regardless of case.
Change By:
Michael DeGuzis
Consider this example: !screenshot-1.png|thumbnail! Jenkinsfile pipeline script via WebUI text input :{code}node('host.domain.com') {env.ARTIFACTORY_SERVER = 'https://host.domain.com/artifactory'env.ABC_VAR = 'abc'env.PYPI_REPO = 'something'try {// clean first so we have the RPMs at the end to look at / test withstage('Cleanup') {cleanWs()} stage('test vars') {echo env.PYPI_REPOecho params.pypi_repo1sh 'echo PYPI_REPO without curly braces is $PYPI_REPO' sh 'echo PYPI_REPO with curly braces is ${PYPI_REPO}' sh "echo PYPI_REPO with double quotes is $PYPI_REPO" sh 'echo ABC_VAR without curly braces is $ABC_VAR'sh 'echo sleeping 5 && sleep 5s' }}catch (err) {currentBuild.result = "FAILURE"throw err}}{code}Results in:{code}[Pipeline] { (test vars) (hide)[Pipeline] echosomething[Pipeline] echouda-pypi-dev[Pipeline] sh+ echo PYPI_REPO without curly braces is somethingPYPI_REPO without curly braces is something[Pipeline] sh+ echo PYPI_REPO with curly braces is somethingPYPI_REPO with curly braces is something[Pipeline] sh+ echo PYPI_REPO with double quotes is somethingPYPI_REPO with double quotes is something[Pipeline] sh+ echo ABC_VAR without curly braces is abcABC_VAR without curly braces is abc[Pipeline] sh+ echo sleeping 5sleeping 5+ sleep 5s{code}Changing the named parameter pypi_repo1 to pypi_repo yields:{code}[Pipeline] { (test vars)[Pipeline] echosomething[Pipeline] echouda-pypi-dev[Pipeline] sh+ echo PYPI_REPO without curly braces isPYPI_REPO without curly braces is[Pipeline] sh+ echo PYPI_REPO with curly braces isPYPI_REPO with curly braces is[Pipeline] sh+ echo PYPI_REPO with double quotes is somethingPYPI_REPO with double quotes is something[Pipeline] sh+ echo ABC_VAR without curly braces is abcABC_VAR without curly braces is abc[Pipeline] sh+ echo sleeping 5sleeping 5+ sleep 5s{code}
Add Comment
[JIRA] (JENKINS-60190) Parameter references clash with variables, regardless of case.
Title: Message Title
Michael DeGuzis updated an issue
Jenkins / JENKINS-60190
Parameter references clash with variables, regardless of case.
Change By:
Michael DeGuzis
Consider this example:! image screenshot - 2019-11-15-14-48-18-933 1 .png |thumbnail ! Jenkinsfile via WebUI:{code}node('host.domain.com') {env.ARTIFACTORY_SERVER = 'https://host.domain.com/artifactory'env.ABC_VAR = 'abc'env.PYPI_REPO = 'something'try {// clean first so we have the RPMs at the end to look at / test withstage('Cleanup') {cleanWs()} stage('test vars') {echo env.PYPI_REPOecho params.pypi_repo1sh 'echo PYPI_REPO without curly braces is $PYPI_REPO' sh 'echo PYPI_REPO with curly braces is ${PYPI_REPO}' sh "echo PYPI_REPO with double quotes is $PYPI_REPO" sh 'echo ABC_VAR without curly braces is $ABC_VAR'sh 'echo sleeping 5 && sleep 5s' }}catch (err) {currentBuild.result = "FAILURE"throw err}}{code}Results in:{code}[Pipeline] { (test vars) (hide)[Pipeline] echosomething[Pipeline] echouda-pypi-dev[Pipeline] sh+ echo PYPI_REPO without curly braces is somethingPYPI_REPO without curly braces is something[Pipeline] sh+ echo PYPI_REPO with curly braces is somethingPYPI_REPO with curly braces is something[Pipeline] sh+ echo PYPI_REPO with double quotes is somethingPYPI_REPO with double quotes is something[Pipeline] sh+ echo ABC_VAR without curly braces is abcABC_VAR without curly braces is abc[Pipeline] sh+ echo sleeping 5sleeping 5+ sleep 5s{code}Changing the named parameter pypi_repo1 to pypi_repo yields:{code}[Pipeline] { (test vars)[Pipeline] echosomething[Pipeline] echouda-pypi-dev[Pipeline] sh+ echo PYPI_REPO without curly braces isPYPI_REPO without curly braces is[Pipeline] sh+ echo PYPI_REPO with curly braces isPYPI_REPO with curly braces is[Pipeline] sh+ echo PYPI_REPO with double quotes is somethingPYPI_REPO with double quotes is something[Pipeline] sh+ echo ABC_VAR without curly braces is abcABC_VAR without curly braces is abc[Pipeline] sh+ echo sleeping 5sleeping 5+ sleep 5s{code}
Add Comment
[JIRA] (JENKINS-60190) Parameter references clash with variables, regardless of case.
Title: Message Title Michael DeGuzis updated an issue Jenkins / JENKINS-60190 Parameter references clash with variables, regardless of case. Change By: Michael DeGuzis Attachment: image-2019-11-15-14-48-18-933.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203153.1573847376000.1736.1573847460233%40Atlassian.JIRA.
[JIRA] (JENKINS-60190) Parameter references clash with variables, regardless of case.
Title: Message Title Michael DeGuzis updated an issue Jenkins / JENKINS-60190 Parameter references clash with variables, regardless of case. Change By: Michael DeGuzis Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203153.1573847376000.1734.1573847460165%40Atlassian.JIRA.
[JIRA] (JENKINS-60190) Parameter references clash with variables, regardless of case.
Title: Message Title
Michael DeGuzis created an issue
Jenkins / JENKINS-60190
Parameter references clash with variables, regardless of case.
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
image-2019-11-15-14-48-18-933.png
Components:
pipeline
Created:
2019-11-15 19:49
Priority:
Major
Reporter:
Michael DeGuzis
Consider this example: Jenkinsfile via WebUI:
node('host.domain.com') {
env.ARTIFACTORY_SERVER = 'https://host.domain.com/artifactory'
env.ABC_VAR = 'abc'
env.PYPI_REPO = 'something'
try {
// clean first so we have the RPMs at the end to look at / test with
stage('Cleanup') {
cleanWs()
}
stage('test vars') {
echo env.PYPI_REPO
echo params.pypi_repo1
sh 'echo PYPI_REPO without curly braces is $PYPI_REPO'
sh 'echo PYPI_REPO with curly braces is ${PYPI_REPO}'
sh "echo PYPI_REPO with double quotes is $PYPI_REPO"
sh 'echo ABC_VAR without curly braces is $ABC_VAR'
sh 'echo sleeping 5 && sleep 5s'
}
}
catch (err) {
currentBuild.result = "FAILURE"
throw err
}
}
Results in:
[Pipeline] { (test vars) (hide)
[Pipeline] echo
something
[Pipeline] echo
uda-pypi-dev
[Pipeline] sh
+ echo PYPI_REPO without curly braces is something
[JIRA] (JENKINS-58094) mTLS client certificates broken in 2.176.1+ by changes in jetty
Title: Message Title
Michael DeGuzis edited a comment on JENKINS-58094
Re: mTLS client certificates broken in 2.176.1+ by changes in jetty
I found an answer for my issue, and I'm still not sure if it's related. For whatever reason, beyond Jenkins 2. 176 164 . 1 3 , the JVM acts as if it no longer is looking at the default trust store at /etc/ssl/certs/java/cacerts. There was no need to import the public cert from our AD LDAP server into the default truststore.{code}export JAVA_OPTS="-Dhudson.plugins.active_directory.ActiveDirectorySecurityRealm.forceLdaps=true \-Dorg.apache.commons.jelly.tags.fmt.timeZone=America/New_York \-Djavax.net.ssl.trustStore=/etc/ssl/certs/java/cacerts \-Djavax.net.ssl.trustStorePassword=changeit"{code}Full docker run:{code}+ sudo docker run -d --name jenkins-server-test --network=jenkins-network --volume jenkins-test-data:/var/jenkins_home --publish 8555:8443 --env 'JAVA_OPTS=-Dhudson.plugins.active_directory.ActiveDirectorySecurityRealm.forceLdaps=true -Dorg.apache.commons.jelly.tags.fmt.timeZone=America/New_York -Djavax.net.ssl.trustStore=/etc/ssl/certs/java/cacerts -Djavax.net.ssl.trustStorePassword=changeit' geisinger-jenkins-test:2.176.2 --sessionTimeout=15 --httpPort=-15 --httpsPort=8443 --httpsKeyStore=/var/jenkins_home/.keystore/host.domain.com.all.jks --httpsKeyStorePassword=*{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200136.1560952087000..1566236760276%40Atlassian.JIRA.
[JIRA] (JENKINS-58094) mTLS client certificates broken in 2.176.1+ by changes in jetty
Title: Message Title Michael DeGuzis commented on JENKINS-58094 Re: mTLS client certificates broken in 2.176.1+ by changes in jetty I found an answer for my issue, and I'm still not sure if it's related. For whatever reason, beyond Jenkins 2.176.1, the JVM acts as if it no longer is looking at the default trust store at /etc/ssl/certs/java/cacerts. There was no need to import the public cert from our AD LDAP server into the default truststore. export JAVA_OPTS="-Dhudson.plugins.active_directory.ActiveDirectorySecurityRealm.forceLdaps=true \ -Dorg.apache.commons.jelly.tags.fmt.timeZone=America/New_York \ -Djavax.net.ssl.trustStore=/etc/ssl/certs/java/cacerts \ -Djavax.net.ssl.trustStorePassword=changeit" Full docker run: + sudo docker run -d --name jenkins-server-test --network=jenkins-network --volume jenkins-test-data:/var/jenkins_home --publish 8555:8443 --env 'JAVA_OPTS=-Dhudson.plugins.active_directory.ActiveDirectorySecurityRealm.forceLdaps=true -Dorg.apache.commons.jelly.tags.fmt.timeZone=America/New_York -Djavax.net.ssl.trustStore=/etc/ssl/certs/java/cacerts -Djavax.net.ssl.trustStorePassword=changeit' geisinger-jenkins-test:2.176.2 --sessionTimeout=15 --httpPort=-15 --httpsPort=8443 --httpsKeyStore=/var/jenkins_home/.keystore/host.domain.com.all.jks --httpsKeyStorePassword=* Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) --
[JIRA] (JENKINS-58094) mTLS client certificates broken in 2.176.1+ by changes in jetty
Title: Message Title Michael DeGuzis commented on JENKINS-58094 Re: mTLS client certificates broken in 2.176.1+ by changes in jetty I wonder if this is also affecting our failure to bind to active directory using the JDK Trustore option of Jenkins > Configure Global Security > Security Ream > Active Directory > TLS Configuration. simple bind failed: LDAP_HOST:636 sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:141) at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:126) at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:280) at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:392) Caused: sun.security.validator.ValidatorException: PKIX path building failed at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:397) at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:302) at sun.security.validator.Validator.validate(Validator.java:262) at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324) at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229) at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1621) Caused: javax.net.ssl.SSLHandshakeException at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1946) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:316) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:310) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1639) at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:223) at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1037) at sun.security.ssl.Handshaker.process_record(Handshaker.java:965) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1064) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367) at sun.security.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:750) at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:123) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140) at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:443) at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:416) at com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:359) at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:214 As soon as I downgrade to 2.164.3, things work fine again. I setup a QA/Test master with only the Active Directory plugin. Thoughts?
[JIRA] (JENKINS-34377) job-restrictions Job Property does not support Pipeline Plugin
Title: Message Title Michael DeGuzis commented on JENKINS-34377 Re: job-restrictions Job Property does not support Pipeline Plugin I don't really see a way to restrict nodes with Authorize Project. Any notes on that or a post that describes that? 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-22) Add a global settings for keep n artifacts/logs
Title: Message Title Michael DeGuzis commented on JENKINS-22 Re: Add a global settings for keep n artifacts/logs Why isn't this a thing? Managing old build logs is terrible and all you would need to do is hook the config from a job into the global options 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-34377) job-restrictions Job Property does not support Pipeline Plugin
Title: Message Title Michael DeGuzis commented on JENKINS-34377 Re: job-restrictions Job Property does not support Pipeline Plugin Hmm ok, I will check into that. I was hoping to restrict this at the node level. I'm not entirely sure how to achieve this with that plugin, but maybe I missed something. 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-34377) job-restrictions Job Property does not support Pipeline Plugin
Title: Message Title Michael DeGuzis commented on JENKINS-34377 Re: job-restrictions Job Property does not support Pipeline Plugin The last update was a year ago, any update? This is one key thing that is holding us back from pinning nodes to certain users so we don't have to use a power user to connect to the nodes and then restrict who can use the node. 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-53708) Cannot use standard CSS comments
Title: Message Title
Michael DeGuzis created an issue
Jenkins / JENKINS-53708
Cannot use standard CSS comments
Issue Type:
Bug
Assignee:
Tobias Gruetzmacher
Components:
simple-theme-plugin
Created:
2018-09-21 15:24
Environment:
Jenkins 2.138.1 Simple Theme Plugin 0.5.1
Priority:
Minor
Reporter:
Michael DeGuzis
Multiline CSS comments or // comments do not work. They break the CSS I used to adjust the image: Invalid:
body {
background-color: #feffd8;
}
/* Uncomment he below to change the logo image */
/*
.logo img {
content:url("https://host:8444/userContent/title.png");
}
*/
*/
login page - See: https://jenkins.io/blog/2018/06/27/new-login-page
See section for Login Theme plugin at Jenkins > Manage Jenkins
*/
.logo #jenkins-name-icon {
content:url("https://host:8444/userContent/title.png");
position: absolute;
bottom: 3px;
left: 40px;
width: 220px;
}
.logo:after {
// Use regular text instead of an image
content: '';
font-weight: bold;
font-size: 20px;
margin-left: 50px;
margin-right: 12px;
color: white;
line-height: 40px;
}
Works:
body {
background-color: #feffd8;
}
.logo #jenkins-name-icon {
content:url("https://host:8444/userContent/title.png");
position: absolute;
bottom: 3px;
left: 40px;
width: 220px;
}
.logo:after {
[JIRA] (JENKINS-37050) Pipeline Job Cannot Checkout Git Tag
Title: Message Title Michael DeGuzis edited a comment on JENKINS-37050 Re: Pipeline Job Cannot Checkout Git Tag Sorry, but this is a bit ridiculous silly that tags are not considered a "simple" use case here. Thousands of projects use a tag for releases. Making them use the GitSCM class to pull a tag is not ideal. The vast majority of our Git workflow uses releases, as do many, many projects. Creating a branch for a release is not the intended workflow of Git. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-37050) Pipeline Job Cannot Checkout Git Tag
Title: Message Title Michael DeGuzis commented on JENKINS-37050 Re: Pipeline Job Cannot Checkout Git Tag Sorry, but this is a bit ridiculous that tags are not considered a "simple" use case here. Thousands of projects use a tag for releases. Making them use the GitSCM class to pull a tag is not ideal. The vast majority of our Git workflow uses releases, as do many, many projects. Creating a branch for a release is not the intended workflow of Git. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-49780) Sidebar-links plugins kills "restrict to" option in GUI build configure
Title: Message Title Michael DeGuzis created an issue Jenkins / JENKINS-49780 Sidebar-links plugins kills "restrict to" option in GUI build configure Issue Type: Bug Assignee: Unassigned Attachments: image-2018-02-27-16-48-34-098.png, image-2018-02-27-16-49-20-867.png Components: sidebar-link-plugin Created: 2018-02-27 21:50 Priority: Major Reporter: Michael DeGuzis Before installing sidebar links, this option is available (our prod instance) After installing sidebar-links,this option is removed: It appears sidebar links trounces that option. Add Comment
