Uploaded image for project: 'repository.jboss.org/nexus'
  1. repository.jboss.org/nexus
  2. NEXUS-980

Don't ignore brand new content for purely 'validation' tasks

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • Q3CY25
    • None
    • Maven Central Plugin
    • None
    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • MWES 2025-08-12

      The 'MCD' and 'Validation' tasks ignore content that is less than 10 minutes old. The reason given for this is it helps avoid partially syncing content to Central that has only partially been deployed.

      This makes sense for MCD, but less so for 'Validation' tasks for staging repos. So the request is that for those the check covers all content in the repo.

      What I'm requiring WildFly project deployers to do is to deploy to a staging repo and run the appropriate Validation task before doing the staging-move to the ultimate repo. I tell them to wait 10 minutes before doing the validation, otherwise they may get a inapplicable result that didn't check their stuff.

      This "wait 10 minutes" instruction is not going to work; for sure people will forget, or not notice it or whatever, as it breaks the natural flow of work. They will stage the content and immediately go to the UI to run the task.

      We've already had one invalid component get moved from 'wildfly-staging' to 'releases' because of this.

              dhladky@redhat.com David Hladky
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: