Branch: refs/heads/master
Home: https://github.com/jenkinsci/acceptance-test-harness
Commit: 5e7654026f6d4e79b3080f5d5e280cb44cf79cb9
https://github.com/jenkinsci/acceptance-test-harness/commit/5e7654026f6d4e79b3080f5d5e280cb44cf79cb9
Author: Andra Maria Puscas <[email protected]>
Date: 2023-09-18 (Mon, 18 Sep 2023)
Changed paths:
M .github/dependabot.yml
M .github/renovate.json
M pom.xml
A
src/main/java/org/jenkinsci/test/acceptance/docker/fixtures/GitLabContainer.java
A
src/main/java/org/jenkinsci/test/acceptance/plugins/gitlab_plugin/GitLabBranchSource.java
A
src/main/java/org/jenkinsci/test/acceptance/plugins/gitlab_plugin/GitLabOrganizationFolder.java
A
src/main/java/org/jenkinsci/test/acceptance/plugins/gitlab_plugin/GitLabPersonalAccessTokenCredential.java
A
src/main/java/org/jenkinsci/test/acceptance/plugins/gitlab_plugin/GitLabServerConfig.java
A
src/main/resources/org/jenkinsci/test/acceptance/docker/fixtures/GitLabContainer/Dockerfile
A
src/main/resources/org/jenkinsci/test/acceptance/docker/fixtures/GitLabContainer/create_user.rb
A src/test/java/plugins/GitLabPluginTest.java
Log Message:
-----------
Gitlab container and tests (#1335)
* add docker fixture for gitlab
* create test
* pin gitlab version
* Remove addSSHCertificate in GitLabContainer
* add createRepo test
* Reword createRepo and add TODO
* add delete repo method
* automatically create a token to be used inside the container and adapt the
methods
* add gitlab to renovate
* wait for gitlab to be running
* Changing over to java http client and cleanup
* modify the wait method
* use repo name in the delete method
* code review
* create multiple users
* configure dependabot for gitlab image
* try port mapping
* fix waitForReady
* test GitLab server configuration
* create separate method for credentials
* configure token in credentials
* remove renovate
* create the multibranch pipeline
* use existing method for repo creation
* use gitlab4j to create branches and MR
* add verification for jobs and add a failed job
* Try to wait for jobs to exist before checking build number
* code review
* create GitLab group and organization folder
* create and test GitLab organization folder
* try and check the builds
* check the builds run
* code review part 1
* code review part 2
* code review part 3
* code review part 4
* refactor and code review
---------
Co-authored-by: Julie Heard <[email protected]>
Co-authored-by: Raul Arabaolaza <[email protected]>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-commits/jenkinsci/acceptance-test-harness/push/refs/heads/master/5d3e2a-5e7654%40github.com.
