[NPMCLI-251] Sometimes does not return snapshot `mgnl jumpstart -s` Created: 04/Feb/21  Updated: 24/Jan/24  Resolved: 24/Jan/24

Status: Closed
Project: Magnolia CLI
Component/s: None
Affects Version/s: None
Fix Version/s: 4.0.6

Type: Bug Priority: Major
Reporter: Šimon Demočko Assignee: Rishab Dhar
Resolution: Done Votes: 1
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by NPMCLI-286 Can not pull snapshot version Closed
relation
is related to NPMCLI-286 Can not pull snapshot version Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[X]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Epic Link: DevX Bucket
Story Points: 3
T-Shirt Size: Small
Team: DeveloperX
Work Started:

 Description   

Steps to reproduce

  1. Create a feature branch on ce/dx-core (the prerequisite is -SNAPSHOT as suffix, see here. 
  2. Once Nexus has a bundle there, trigger mgnl jumpstart -s

Expected results

You should receive latest magnolia bundle snapshot.

Actual results

Instead, you'll receive a bundle built on that feature branch. (can be observed by the downloaded snapshot name in terminal, when triggering jumpstart command)



 Comments   
Comment by Federico Grilli [ 18/Feb/21 ]

As a workaround, I think you can specify the -m parameter (stands for "magnolia version") at command line,
e.g mgnl jumpstart -s -m 6.2.7. Otherwise, the LATEST version will be used which apparently Nexus interprets as "the latest deployed artifact with the chosen name and group id in that repository".

Comment by Christopher Zimmermann [ 15/Jun/21 ]

This tripped me up when trying to test a new feature on snapshot. I had to waste some time with Roman to figure out this was the problem. We should fix soon for our own sanity.

Comment by Christopher Zimmermann [ 13/Dec/23 ]

Update. The problem is slightly different now due to the addition of 6.3 branches. 

Today: with the `-s` command gets: The webapp version is magnolia-community-webapp-6.3-SearchX-1-20231205.134257-33.war.
But we expect that we will get the latest version of 6.2-SNAPSHOT,

Generated at Mon Feb 12 04:47:59 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.