Files in Artifacts are dated in the future

Viewed 11

This issue began a little over a week ago. The build pipelines are creating artifacts whose files are dated four hours in the future. When doing a release those files are not able to be copied to the server because they are in the future. I went into user settings and every person on my team showed the Time and Locale four hours in the future. The organization owner went into the organization settings and changed the time zone to UTC-5:00 Eastern Time. Our Region is East US 2. Once saved everyone's builds began creating artifacts with the correct time for the files that were compiled. Except for me. I have tried:

  • Logging out and back in
  • Deleting the pipeline and recreating it
  • Trying in different projects
  • Trying it on different machines
  • Doing what MS suggested:

Try these first to see if they work: • Open Start, type: CMD • Right click CMD • Click Run as administrator • Type in at the prompt OR Copy and Paste these one at a time : (Hit enter after each) • Dism /Online /Cleanup-Image /CheckHealth • Dism /Online /Cleanup-Image /ScanHealth • Dism /Online /Cleanup-Image /RestoreHealth Also run the System File Checker utility: • Open Start, type: CMD • Right click CMD • Click Run as administrator • At the Command Prompt, type: sfc/scannow • This will check for any integrity violations • Restart your system Check your hard disk for any errors: • Click Start • Type: CMD, from the results, right click Command prompt • Click 'Run as Administrator' • At the Command Prompt, type: chkdsk /r /f • Hit Enter • When you restart your system, your computer will be scanned for errors and attempts will be made to correct them.

  • Deleting my other Organization that I use for training classes

That about sums it up. Whenever I do a manual build or a triggered build this happens and I have to wait four hours to release it. ANY help is much appreciated.

0 Answers
Related