Wow that is good point. I think if build of asjs is being done by Maven it will be taken from 0.9.6-SNAPSHOT I think so. It definitely won't use staged compiler - You need to point such stuff explicitly using settings.xml
On Tue, Aug 13, 2019, 10:20 PM Alex Harui <[email protected]> wrote: > I'm not sure you should skip the uploading. I'm not sure where typedefs > and asjs will get its compiler artifacts if they haven't been uploaded. > > The output says that it is looking in the following folder for artifacts: > > > d:\Work\royale-sources\royale-compiler\royale096\sources\royale096\artifacts\archive\target\checkout\release-dir > > For me, my temp folder is: > > ~/temp/releasesteps > > And the artifacts are in: > > artifacts/archive/target/checkout/release-dir > > There seems to be another level in there for you (sources\royale096). > > HTH, > -Alex > > On 8/13/19, 11:31 AM, "Piotr Zarzycki" <[email protected]> wrote: > > Sorry about that. I was going trough the steps but I have left steps > for > signing artifacts and uploading them at the end. > > When for all 3 repos I had build, comparison and sign in works I tried > upload it using provided instructions. > > If you are not seeing any suspicious in that log I need to understand > more > why actually upload wasn't triggered. > > Artifacts were definitely generated correctly. > > Thanks, > Piotr > > On Tue, Aug 13, 2019, 5:33 PM Alex Harui <[email protected]> > wrote: > > > I'm not sure what warnings you are referring to. > > > > If you look at releasesteps.xml, you can see that it is using Maven's > > wagon:upload goal to upload from a particular folder. Are there > jars in > > that folder (or its subfolders)? Examine the output of the previous > Ant > > release steps for step 003 to see if the source package built > correctly and > > binary matched. If the previous steps were successful then the > upload > > should be picking up those artifacts. > > > > I'm a bit confused that you got to step 11 according to email but > now are > > saying you never got past step 3. > > > > Also, I do not recommend using a temporary folder inside your working > > copy. It will be far safer to specify an absolute path to a folder > outside > > of your working copy. Find a good place to add that to the wiki > > instructions. > > > > HTH, > > -Alex > > > > On 8/13/19, 2:02 AM, "Piotr Zarzycki" <[email protected]> > wrote: > > > > Hi Alex, > > > > Thanks for information. I went today trough the steps again. I > reached > > point where I'm trying to upload artifacts, but script keep > saying me > > that > > there is nothing to upload. Is it because of those warnings at > the > > beginnings ? [1] > > > > [1] > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fzvxoi&data=02%7C01%7Caharui%40adobe.com%7Cf5df4b604e16410f44a808d7201c803a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013179110163174&sdata=4hzhaPPkBXhC4ACCdnZ1GEym6MRSVVsIhisRLT8vvjs%3D&reserved=0 > > > > Thanks, > > Piotr > > > > pon., 12 sie 2019 o 19:31 Alex Harui <[email protected]> > > napisał(a): > > > > > Getting back to this. > > > > > > You can start a vote on the results. If we get this process > > working, it > > > should be relatively easy for others to do releases as well so > we > > will > > > hopefully do releases more often and it won't matter if > someone's > > recent > > > changes made it into the RC or not. > > > > > > Also, the other committers should be aware that an RC is being > > created > > > because they see the emails being sent by the CI server and > ask the > > RM to > > > agree to accept a commit to the release branch instead of the > develop > > > branch. > > > > > > The only build output I could find on the server for the 7/24 > both > > show > > > that the date/time given back in step 009 was invalid. As you > can > > see from > > > the exception, Java is parsing the string and the expectation > is > > that the > > > string you enter conforms to the Java format of: > > > > > > MM/dd/yy HH:mm Z > > > > > > The documentation for this format is in the Java > documentation. As I > > > explained in an earlier reply, "Z" stands for timezone and you > must > > supply > > > one. It shouldn't matter which one you supply, I use the one > I'm > > in, but > > > again, the whole point of this exercise is to find bugs and > improve > > > documentation of the process. In your most recent attempt, > you did > > not > > > specify a timezone. In the one prior, you did not supply a > year or > > a space > > > between date and hour. Please update the documentation or the > > instructions > > > in the Jenkins jobs to make it more clear that you have to be > > accurate in > > > specifying the date. > > > > > > HTH, > > > -Alex > > > > > > On 7/24/19, 9:01 AM, "Piotr Zarzycki" < > [email protected]> > > wrote: > > > > > > Btw. Once I finish steps - Can I publish artefacts and > start RC1 > > vote > > > on > > > dev ? Does anything I should know at the end which is not > > mention ? > > > > > > > > > śr., 24 lip 2019 o 17:59 Piotr Zarzycki < > > [email protected]> > > > napisał(a): > > > > > > > By compare to dypedefs step - do you mean that I should > look > > into > > > Jenkins > > > > configuration of that steps or something else ? > > > > > > > > śr., 24 lip 2019 o 17:56 Alex Harui > <[email protected]> > > > napisał(a): > > > > > > > >> Hi Piotr, > > > >> > > > >> You can compare the output from previous builds and > also the > > > typedefs > > > >> build configuration because both successfully used the > date > > > format. The > > > >> Java documentation says that "Z" is for timezone. It > > shouldn't > > > matter > > > >> which one you use, but in the typedefs you hadn't > specified > > one at > > > all. > > > >> > > > >> It looks like in this case extra quotes are wrapped > around > > the date. > > > >> You'll have to compare against the typedefs steps to > see why > > that's > > > >> happening. > > > >> > > > >> HTH, > > > >> -Alex > > > >> > > > >> On 7/24/19, 3:53 AM, "Piotr Zarzycki" < > > [email protected]> > > > wrote: > > > >> > > > >> Hi Alex, > > > >> > > > >> I was able to overcome issue with date for typedefs. > > Instruction > > > >> there is > > > >> saying: > > > >> > > > >> MM/dd/yy HH:mm Z > > > >> > Where MM/dd/yy is the US-formatted date and HH:MM > is a > > faked > > > time to > > > >> > encode the release version such as: > > > >> > 2/10/19 9:06 -0800 > > > >> > > > >> > > > >> I have typed 7/24/2019 HH (I don't remember what was > > that) and > > > -0800 > > > >> - This > > > >> part I completely do not understand - what is for > there > > minus ? > > > Can > > > >> you > > > >> send exact example of what I should put there ? > > > >> > > > >> What's more I have went trough forward and in steps > > related to > > > >> royale-asjs > > > >> I see that typing either > > > >> > > > >> 7/24/19 9:06 -0800 or just 7/24/19 9:06 causes an > > exception > > > with > > > >> following > > > >> message: > > > >> > > > >> > > > >> [INFO] COMPC > > > >> [INFO] Loading configuration: > > > >> > > > >> > > > > > > C:\jenkins\workspace\Royale_Release_Step_011\target\checkout\frameworks\themes\Jewel-Dark-NoFlat-Emphasized-Yellow-Theme\target\compile-swf-config.xml > > > >> [INFO] > > > >> [INFO] java.text.ParseException: Unparseable date: > > ""7/24/19 > > > 9:06"" > > > >> [INFO] at > > java.text.DateFormat.parse(DateFormat.java:366) > > > >> [INFO] at > > > >> > > > > > > org.apache.royale.compiler.internal.targets.SWCTarget.processFileEntry(SWCTarget.java:330) > > > >> [INFO] at > > > >> > > > > > > org.apache.royale.compiler.internal.targets.SWCTarget.addFileEntriesToSWC(SWCTarget.java:291) > > > >> > > > >> It looks like there are some additional parentheses > - > > Maybe > > > it's an > > > >> issue. > > > >> > > > >> > > > >> Thanks, > > > >> > > > >> Piotr > > > >> > > > >> > > > >> wt., 23 lip 2019 o 18:56 Alex Harui > > <[email protected]> > > > >> napisał(a): > > > >> > > > >> > Hi Piotr, > > > >> > > > > >> > What differences did you see? I downloaded the > two > > SWCs and > > > the > > > >> only > > > >> > difference I saw was the timestamps in the > catalog.xml > > in the > > > SWCs. > > > >> > > > > >> > The timestamps are set by the SWCDATE parameter > in Step > > 005. > > > The > > > >> log > > > >> > indicates that you did not specify a timezone so > maybe > > that's > > > why > > > >> the > > > >> > timestamps are not matching up. Please update the > > > instructions so > > > >> that > > > >> > future RMs do not forget to include a timezone. > The > > example > > > >> pattern that > > > >> > Jenkins should show should include a timezone. > > > >> > > > > >> > You will have to remove the tag and revert any > commits > > from > > > steps > > > >> 5, 6, > > > >> > and 7 before re-running step 5. > > > >> > > > > >> > HTH, > > > >> > -Alex > > > >> > > > > >> > On 7/23/19, 6:57 AM, "Piotr Zarzycki" < > > > [email protected]> > > > >> wrote: > > > >> > > > > >> > Hi Alex, > > > >> > > > > >> > Thanks! I have moved forward and in step 7 - > > related to > > > >> typedefs during > > > >> > build on my local machine I got mismatch > error [1]. > > What > > > could > > > >> actually > > > >> > happen? I did compare some files inside those > two > > swc and > > > they > > > >> are > > > >> > indeed > > > >> > different - I have used Total Command to > compare > > them. > > > >> > > > > >> > When I'm starting steps related to typedefs - > first > > step > > > >> actually > > > >> > checkout > > > >> > fresh sources ? I'm wondering whether Jenkins > > checkout > > > them > > > >> earlier > > > >> > when I > > > >> > started one of the step before typedefs > steps? This > > those > > > 2 > > > >> files [2] > > > >> > > > > >> > [1] > > > >> > > > > >> > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fbren2&data=02%7C01%7Caharui%40adobe.com%7Cf5df4b604e16410f44a808d7201c803a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013179110173173&sdata=%2Ba9NxCNjcO08f8ZbgePErL1SZvxaD6lpSn6DsQbr8Ik%3D&reserved=0 > > > >> > [2] > > > >> > > > > >> > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2F1drv.ms%2Fu%2Fs!ApVpLyjpHDC2icJBcCsTMZrzfnTTuQ%3Fe%3DNwidMg&data=02%7C01%7Caharui%40adobe.com%7Cf5df4b604e16410f44a808d7201c803a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013179110173173&sdata=ClD%2BCcEcZ1%2BzRznkEpiECFV7x%2FYjwVKxUs3%2Bcp9Fay0%3D&reserved=0 > > > >> > > > > >> > Thanks, > > > >> > Piotr > > > >> > > > > >> > wt., 23 lip 2019 o 07:31 Alex Harui > > > <[email protected]> > > > >> > napisał(a): > > > >> > > > > >> > > Hi Piotr, > > > >> > > > > > >> > > The email with the subject "Release Step 003 > > Succeeded" > > > says: > > > >> > > > > > >> > > 1. If you are releasing the utils jars > > > (compiler-jburg-types > > > >> and > > > >> > > compiler-build-tools), Run: > > > >> > > ant -f releasesteps.xml Release_Step_003 > > -Dutils=true > > > >> > > -Drelease.version=0.9.6 > > > >> > > > > > >> > > It looks like you are not using the > -Dutils=true. > > > Please > > > >> improve the > > > >> > > email so future RMs will not miss that > parameter. > > > >> > > > > > >> > > Thanks, > > > >> > > -Alex > > > >> > > > > > >> > > On 7/22/19, 9:06 AM, "Piotr Zarzycki" < > > > >> [email protected]> > > > >> > wrote: > > > >> > > > > > >> > > Hi Alex, > > > >> > > > > > >> > > I have made adjustment to > documentation. I'm > > on > > > step 3 > > > >> where I > > > >> > need > > > >> > > build > > > >> > > on my end sources. I have run on my PC > this: > > > >> > > > > > >> > > ant -f releasesteps.xml Release_Step_003 > > > >> -Drelease.version=0.9.6 > > > >> > > > > > >> > > It downloads sources and maven > artifacts, but > > it > > > also > > > >> tried > > > >> > build them > > > >> > > automatically as I understa. I got > error [1] > > - it > > > >> understandable > > > >> > cause > > > >> > > there is no 1.0.0 compiler-jburg-types. > > Should I on > > > my > > > >> own build > > > >> > > first compiler-jburg-types with 1.0.0 > to have > > stuff > > > in > > > >> local > > > >> > cache or > > > >> > > should I made something else ? > > > >> > > > > > >> > > [1] > > > >> > > > > > >> > > > > >> > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fa10nq&data=02%7C01%7Caharui%40adobe.com%7Cf5df4b604e16410f44a808d7201c803a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013179110173173&sdata=4dlbh3xDClPiFNz%2BIYPy2X8QQvAsVuAaIUcuKZZVcSw%3D&reserved=0 > > > >> > > > > > >> > > Thanks, > > > >> > > Piotr > > > >> > > > > > >> > > sob., 20 lip 2019 o 06:25 Alex Harui > > > >> <[email protected]> > > > >> > > napisał(a): > > > >> > > > > > >> > > > Please update the wiki in a way that > the > > next > > > person > > > >> will know > > > >> > which > > > >> > > 2FA > > > >> > > > token to use. > > > >> > > > > > > >> > > > Thanks, > > > >> > > > -Alex > > > >> > > > > > > >> > > > On 7/19/19, 9:08 AM, "Piotr Zarzycki" > < > > > >> > [email protected]> > > > >> > > wrote: > > > >> > > > > > > >> > > > So far so good. I'm on a step 3, > where > > I need > > > build > > > >> > artifacts on > > > >> > > my > > > >> > > > sight > > > >> > > > and compare them with what Jenkins > > produce. > > > >> > > > > > > >> > > > I will get back to that probably > on > > Monday. > > > >> > > > > > > >> > > > On Fri, Jul 19, 2019, 1:40 PM > Piotr > > Zarzycki < > > > >> > > > [email protected]> > > > >> > > > wrote: > > > >> > > > > > > >> > > > > Hi Alex, > > > >> > > > > > > > >> > > > > Thanks it's working. I'm moving > > forward > > > with that > > > >> stuff > > > >> > let's > > > >> > > see > > > >> > > > how far > > > >> > > > > I go with it. > > > >> > > > > > > > >> > > > > Piotr > > > >> > > > > > > > >> > > > > pt., 19 lip 2019 o 05:49 Alex > Harui > > > >> > <[email protected]> > > > >> > > > napisał(a): > > > >> > > > > > > > >> > > > >> I am using the token generated > this > > way: > > > >> > > > >> > > > >> > > > >> > > > >> > > > > > > >> > > > > > >> > > > > >> > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.github.com%2Fen%2Farticles%2Fcreating-a-personal-access-token-for-the-command-line&data=02%7C01%7Caharui%40adobe.com%7Cf5df4b604e16410f44a808d7201c803a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013179110173173&sdata=X5X8efqqzwvC1rxG4AwVnAZK6ThBKimPB3Nl61yGQFM%3D&reserved=0 > > > >> > > > >> > > > >> > > > >> There is no short code from > Google > > > Authenticator. > > > >> > > > >> > > > >> > > > >> -Alex > > > >> > > > >> > > > >> > > > >> On 7/18/19, 8:46 AM, "Piotr > > Zarzycki" < > > > >> > > [email protected]> > > > >> > > > wrote: > > > >> > > > >> > > > >> > > > >> I'm using 2FA > authentication, > > second > > > step > > > >> for me is > > > >> > typing > > > >> > > > short code > > > >> > > > >> from > > > >> > > > >> Google Authenticator > > application. Do > > > you use > > > >> > something > > > >> > > > different? > > > >> > > > >> > > > >> > > > >> czw., 18 lip 2019 o 17:42 > Alex > > Harui > > > >> > > <[email protected]> > > > >> > > > >> napisał(a): > > > >> > > > >> > > > >> > > > >> > I don't think git version > > matters. > > > Are you > > > >> using > > > >> > your > > > >> > > 2fa > > > >> > > > token as > > > >> > > > >> the > > > >> > > > >> > password? It should be a > > really long > > > >> sequence of > > > >> > > characters. > > > >> > > > >> > > > > >> > > > >> > Get Outlook for Android< > > > >> > > > >> > > > >> > > > > > > >> > > > > > >> > > > > >> > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fghei36&data=02%7C01%7Caharui%40adobe.com%7Cf5df4b604e16410f44a808d7201c803a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013179110173173&sdata=aXoDU8eCG50R2hjNTX5%2FdLIfILY932F86hCQ86aBwWU%3D&reserved=0 > > > >> > > > >> > > > > >> > > > >> > > > > >> > > > >> > > > ________________________________ > > > >> > > > >> > From: Piotr Zarzycki < > > > >> [email protected]> > > > >> > > > >> > Sent: Thursday, July 18, > 2019 > > > 7:43:44 AM > > > >> > > > >> > To: > [email protected] > > > >> > > > >> > Subject: Re: Discuss of > > release steps > > > >> preparation > > > >> > > > >> > > > > >> > > > >> > Maybe Git just should be > > updated on > > > >> Machine ? I > > > >> > see > > > >> > > 2.15 and > > > >> > > > there > > > >> > > > >> is 2.22 > > > >> > > > >> > already. > > > >> > > > >> > > > > >> > > > >> > czw., 18 lip 2019 o > 16:35 Piotr > > > Zarzycki < > > > >> > > > [email protected] > > > >> > > > >> > > > > >> > > > >> > napisał(a): > > > >> > > > >> > > > > >> > > > >> > > When I do git push - > I'm > > getting > > > separate > > > >> > window with > > > >> > > title > > > >> > > > >> GitHub Login > > > >> > > > >> > - > > > >> > > > >> > > where I can enter my > > > login/password. I'm > > > >> doing > > > >> > that > > > >> > > and in > > > >> > > > the > > > >> > > > >> next step > > > >> > > > >> > it > > > >> > > > >> > > throws me an error in > the > > console > > > - same > > > >> what I > > > >> > have > > > >> > > pasted > > > >> > > > in > > > >> > > > >> previous > > > >> > > > >> > > email. > > > >> > > > >> > > > > > >> > > > >> > > I'm typing again login > and > > password > > > >> cause It's > > > >> > asking > > > >> > > me as > > > >> > > > you > > > >> > > > >> can see > > > >> > > > >> > in > > > >> > > > >> > > the previous email. In > the > > results > > > I get: > > > >> > > > >> > > > > > >> > > > >> > > > > > >> > > > >> > > remote: Invalid > username or > > > password. > > > >> > > > >> > > fatal: Authentication > failed > > for ' > > > >> > > > >> > > > > > >> > > > >> > > > > >> > > > >> > > > >> > > > > > > >> > > > > > >> > > > > >> > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-compiler%2F&data=02%7C01%7Caharui%40adobe.com%7Cf5df4b604e16410f44a808d7201c803a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013179110173173&sdata=UrZ3i2tKBU53GUOU2sSnFdkibWycS06Gs%2BghnXXm8Qs%3D&reserved=0 > > > >> > > > >> > ' > > > >> > > > >> > > > > > >> > > > >> > > Does your steps look > the > > same ? > > > >> > > > >> > > > > > >> > > > >> > > > > > >> > > > >> > > > > > >> > > > >> > > > > > >> > > > >> > > czw., 18 lip 2019 o > 16:31 > > Piotr > > > Zarzycki > > > >> < > > > >> > > > >> [email protected]> > > > >> > > > >> > > napisał(a): > > > >> > > > >> > > > > > >> > > > >> > >> I did that and I'm > getting > > wrong > > > >> password or > > > >> > user > > > >> > > name, so > > > >> > > > that > > > >> > > > >> must be > > > >> > > > >> > >> different case. Let > me try > > now > > > again. > > > >> > > > >> > >> > > > >> > > > >> > >> czw., 18 lip 2019 o > 16:21 > > Alex > > > Harui > > > >> > > > <[email protected]> > > > >> > > > >> > >> napisał(a): > > > >> > > > >> > >> > > > >> > > > >> > >>> It is asking for your > > GitHub > > > >> username. Type > > > >> > it in > > > >> > > and hit > > > >> > > > >> enter, then > > > >> > > > >> > >>> it will ask for your > > GitHub 2FA > > > >> token. We > > > >> > don't > > > >> > > store our > > > >> > > > >> credentials > > > >> > > > >> > on > > > >> > > > >> > >>> the machine. > That's why > > the > > > >> Succeeded email > > > >> > says > > > >> > > you > > > >> > > > will > > > >> > > > >> need your > > > >> > > > >> > GH > > > >> > > > >> > >>> credentials. > > > >> > > > >> > >>> > > > >> > > > >> > >>> HTH, > > > >> > > > >> > >>> -Alex > > > >> > > > >> > >>> > > > >> > > > >> > >>> On 7/18/19, 7:06 AM, > "Piotr > > > Zarzycki" < > > > >> > > > >> [email protected]> > > > >> > > > >> > >>> wrote: > > > >> > > > >> > >>> > > > >> > > > >> > >>> In the first > step I'm > > getting > > > >> following > > > >> > error > > > >> > > during > > > >> > > > an > > > >> > > > >> attempt of > > > >> > > > >> > >>> login: > > > >> > > > >> > >>> > > > >> > > > >> > >>> > > > >> > > > >> > >>> git push > > > >> > > > >> > >>> fatal: > > HttpRequestException > > > >> encountered. > > > >> > > > >> > >>> An error > occurred > > while > > > sending > > > >> the > > > >> > request. > > > >> > > > >> > >>> Username for ' > > > >> > > > >> > >>> > > > >> > > > >> > > > > >> > > > >> > > > >> > > > > > > >> > > > > > >> > > > > >> > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com&data=02%7C01%7Caharui%40adobe.com%7Cf5df4b604e16410f44a808d7201c803a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013179110173173&sdata=TLwC7zwvkxeJNyfG0Cffr1ma6Z8BaZnAyhHphJcDADI%3D&reserved=0 > > > >> > > > >> > >>> ': > > > >> > > > >> > >>> > > > >> > > > >> > >>> There is being > > suggestion > > > how to > > > >> resolve > > > >> > it > > > >> > > here [1], > > > >> > > > but > > > >> > > > >> I'm not > > > >> > > > >> > >>> sure > > > >> > > > >> > >>> whether I can do > that > > on > > > remote PC > > > >> ? > > > >> > > > >> > >>> > > > >> > > > >> > >>> [1] > > > >> > > > >> > >>> > > > >> > > > >> > >>> > > > >> > > > >> > > > > >> > > > >> > > > >> > > > > > > >> > > > > > >> > > > > >> > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodeshare.co.uk%2Fblog%2Fhow-to-solve-the-github-error-fatal-httprequestexception-encountered%2F&data=02%7C01%7Caharui%40adobe.com%7Cf5df4b604e16410f44a808d7201c803a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013179110173173&sdata=7St0nBmiwOk%2FC11EquDqo8pznnr15MefTZyUJ9iQxBM%3D&reserved=0 > > > >> > > > >> > >>> > > > >> > > > >> > >>> Thanks, > > > >> > > > >> > >>> Piotr > > > >> > > > >> > >>> > > > >> > > > >> > >>> czw., 18 lip > 2019 o > > 15:06 > > > Piotr > > > >> Zarzycki < > > > >> > > > >> > > [email protected]> > > > >> > > > >> > >>> napisał(a): > > > >> > > > >> > >>> > > > >> > > > >> > >>> > Hi Alex, > > > >> > > > >> > >>> > > > > >> > > > >> > >>> > I'm getting > back to > > that. > > > Again > > > >> some > > > >> > > questions: > > > >> > > > >> > >>> > > > > >> > > > >> > >>> > I think you > will > > need to > > > set up > > > >> your PC > > > >> > for > > > >> > > most, > > > >> > > > if not > > > >> > > > >> all, of > > > >> > > > >> > >>> the steps > > > >> > > > >> > >>> >> in [1] in > order to > > > >> compare/verify the > > > >> > output > > > >> > > from > > > >> > > > [2]. > > > >> > > > >> > >>> > > > > >> > > > >> > >>> > > > > >> > > > >> > >>> > Above means > that I > > don't > > > need to > > > >> setup > > > >> > my own > > > >> > > PC > > > >> > > > fully, > > > >> > > > >> but just > > > >> > > > >> > >>> to be > > > >> > > > >> > >>> > able to build > > project, so > > > could > > > >> compare > > > >> > the > > > >> > > results > > > >> > > > of > > > >> > > > >> build with > > > >> > > > >> > >>> what > > > >> > > > >> > >>> > Jenkins > produce ? > > > >> > > > >> > >>> > However you are > > saying > > > later > > > >> that you > > > >> > didn't > > > >> > > setup > > > >> > > > step > > > >> > > > >> where > > > >> > > > >> > >>> there is > > > >> > > > >> > >>> > produced > > dist/release > > > folder. > > > >> What I > > > >> > got > > > >> > > when I > > > >> > > > launch > > > >> > > > >> each of > > > >> > > > >> > >>> those > > > >> > > > >> > >>> > step actually > at the > > end ? > > > >> > > > >> > >>> > Before you > answer me > > I will > > > >> study and > > > >> > launch > > > >> > > each > > > >> > > > of step > > > >> > > > >> on > > > >> > > > >> > >>> Jenkins to > > > >> > > > >> > >>> > see what will > happen. > > > >> > > > >> > >>> > > > > >> > > > >> > >>> > Thanks, > > > >> > > > >> > >>> > Piotr > > > >> > > > >> > >>> > > > > >> > > > >> > >>> > pon., 8 lip > 2019 o > > 16:59 > > > Piotr > > > >> Zarzycki > > > >> > < > > > >> > > > >> > > [email protected] > > > >> > > > >> > >>> > > > > >> > > > >> > >>> > napisał(a): > > > >> > > > >> > >>> > > > > >> > > > >> > >>> >> Hi, > > > >> > > > >> > >>> >> > > > >> > > > >> > >>> >> I'm occupied > till > > at least > > > >> Wednesday > > > >> > with > > > >> > > important > > > >> > > > >> task, so I > > > >> > > > >> > >>> hope to > > > >> > > > >> > >>>
