Jenkins +gitlab encounters git code inconsistency.

[one...@gmail.com]

hello everybody

The problems I have encountered with Jenkins +gitlab are as follows:

1. Developers upload code to gitlab.

2. Jenkins pulls the code down and packages it (maven)

3. It is now found that the code on Jenkins pull is inconsistent with the code on gitlab, not the latest.

I haven't had this problem before.

I need your help.

Thank you!

[Mark Waite]

You'll need to provide much more detail of the context where you're seeing that problem, the investigation you've done to understand the problem, and the cases where it behaves correctly.

For example:

- What type of job is being used (freestyle, pipeline, multi-branch pipeline, maven, ...)?

- What is the branch specification being used (master, origin/master, */master, */*, ...)?

- Does a different branch specification behave differently (for example, does origin/master behave differently than */master)?

- What Jenkins version are you using?

- What git plugin version are you using?

- What git client plugin version are you using?

- Are there any suspicious or surprising messages in the build log?

- How does your situation compare with https://issues.jenkins-ci.org/browse/JENKINS-37263 ?

- How does your situation compare with other bug reports?

- Is the bug repeatable in a different job?

- Does the bug persist if you copy the problem job to a new job name?

- Does the bug appear with any other repository, or is it limited to a specific repository?

Mark Waite

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/f9eae6b0-1e79-4b61-a56b-1a83ab0705ac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.