mvn hpi:runcommand to run/debug it. I was wondering, this is spawning me a single instance jenkins, is there a way to spawn nodes as well ?
I am new to this channel and wanted to contribute in jenkins infra. I have visited the https://github.com/jenkins-infra/charts/blob/main/CONTRIBUTING.md but still facing issue where to start from.
can anyone help me to get started with ? I have skills on docker, k8s, helm
checkout scmin the Jenkinsfile and is directly configured in the job. I thought I had a solution by doing a
run.getAction(BuildData.class)but I discovered that I don't always get the data of this SCM (for instance if global libraries are imported). So I guess I was just lucky but this isn't the correct way to find it. Do you have any clue about where I should look at ?
hpifile and install it, or place a reference to the
hpifile in your plugins.txt file (if you manage plugin versions as code).
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.