Follow up of story #17178
- When a git commit is pushed to gitlab, Gitlab triggers the Tuleap webhook. Tuleap parses the pushed commits to create cross references.
- The cross reference is created when the pattern "
TULEAP-XXXX" (case insensitive) is used in git commit message and that XXXX is a valid artifact.
- On Tuleap side, it creates a
gitlab_commit #myrepo/sha1 reference that can be used consistently across tuleap.
- In artifact view (only, not in modals) the display of gitlab commit cross references is made with a table (instead of a comma separated list of refs)
- The same kind of display is applied to Tuleap git commits (consistency)
- The last push date is recorded so it can be used to display the "gitlab git repo" with an accurate date (order by last push)
Expected new display of cross ref
The new look & feel (tiles based) is applied for all cross references:
- gitlab_commit, git, tracker natures are displayed with extended informations
- other references are displayed with the "current" level of information aka mostly the id.