Received status code 401 from server: Unauthorized, even I can connect to the repository and deploy artifacts manually. Also, I tried setup automatic CD, but the problem is all scripts are prepared only for maven, but I am using gradle. I deployed artifacts manually, but it seems
update centernever gets update. What is the correct way to publish plugins nowadays from gradle build system?
First of all: you should not cross post because you did not get an answer in 5 minutes.
So basically both channels are appropriate for your question. Are you writing the test for your plugin or a test for the configuration-as-code plugin itself? Additionally, what exactly is your "massive trouble", do you have some logs?
Sorry for cross posting. Wasn't sure which one would be better. Won't do this again. 😳
I'm writing a test for how to configure the Gitea plugin (jenkinsci/configuration-as-code-plugin#1791). Tests pass for configuring Gitea servers globally. Now I'd like to add a test for configuring an organization folder with Gitea as "SCM source" using job-dsl. Right now it fails due to missing "branch-api" plugin. The Gitea plugin depends on it. Within the test suite for configuration-as-code that "branch-api" plugin it is already added to the test scope so based on the developers guide for testing with dependent plugins this should work.
In the build logs it says that the plugin does not match the minimum required version (https://github.com/jenkinsci/configuration-as-code-plugin/runs/4341874964?check_suite_focus=true#step:5:556). This confuses me because I've tried to set the version to the latest one and it doesn't work either. That makes me think that the "branch-api" plugin is not loaded at all or failed to load silently.
After experimenting a bit with various job-dsl scripts (e.g. just configuring a freestyle job) it seems to be related to the "organizationFolder" block. Having that in the script to load breaks the test execution and gives that error message. So I'm guessing that I'm not yet at the point where Gitea plugin is active as it breaks prior to that.
@WithPluginannotation on the test case, which tries to load the "branch-api" plugin but fails as it depends on two other plugins. I've no idea if this annotation overrides all the other potentially loaded plugins or this is a hint for missing plugins in the test scope. I've added both plugins (cloudbees-folder, scm-api) to the pom.xml but no success.
Hi all. I'd want to contribute to the GitLab plugin but I can't register for a new account at https://accounts.jenkins.io/
I get an error page with the message "I am sorry to no be able to answer your request
Feel free to tell me what happened on one of the chat channels: www.jenkins.io/chat/ for details."
Can anyone advise on how to proceed?
Wrong channel, this channel is about people who just starting contributing to Jenkins.
Maybe that helps: https://groups.google.com/g/jenkinsci-dev/c/t0Q0UcSAJK4/m/kukgmscqAgAJ
Hi All, I am new to jenkins and was trying to create a simple pipeline using Jenkinsfile from GIT SCM. However while giving the GIT URL for my repository I am getting below error, can someone please help me or redirect my issue to the concerned resource. Thanks
Failed to connect to repository : Error performing git command: git ls-remote -h
@NehaMittal3010 can you describe what you're trying to do?
Maybe the conversations on those two pull requests will help you on your journey
@MarkEWaite @halkeye i have installed the plugin from Manage Jenkins --> Manage Plugins .. "https://plugins.jenkins.io/uno-choice/" when i ran the security scans below vulnerability are encountered:- JQuery 1.12.4 contains multiple vulnerabilities:
CVE-2020-11022 dated 2020-04-29 has a CVSS score of 6.9.
CVE-2020-11023 dated 2020-04-29 has a CVSS score of 6.9
CVE-2015-9251 dated 2015-01-18 has a CVSS score of 6.1.
CVE-2019-11358 dated 2019-04-19 has a CVSS score of 6.1. i want to uplift the JQuery inside the Active choice Plugin.. i donot know how to create the plugin as i am new to this.. can u please assist me.
If you'd like to see my first few steps on the "Contributing to Open Source" path, see: