Re: [PATCH] Add .gitlab-ci.yml for pdf generation and testing on Gitlab.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2023-02-02 at 23:42 +0900, Akira Yokosawa wrote:
> On Thu, 02 Feb 2023 01:37:02 -0300, Leonardo Brás wrote:
> [...]
> > 
> > It looks like it can be done by "Running CI/CD for external repositories".

Nah, it looks like this won't work either. After my patch on top of master, it's
already warning about diverging repositories when I try to sync.

Another solution I could find:
- Change the patch I sent before to keep the file on another directory, even
with a different name: this will not trigger the build for anyone.
- Change my repository config to trigger the CI from that file.

The file would only be a random YML file in the repo.
Would that be ok?

> > 
> > I removed my previous repository and then imported perfbook again using the
> > above mentioned mode. According to the man page, it will run CI for the project
> > whenever a new push to the referenced repository happens.
> > 
> > So it's just a matter of waiting a new commit getting push'ed to see if it will
> > be working.
> 
> Hi Leonardo,
> 
> I noticed a minor glitch in the generated PDFs.
> They don't have Git commit info in the title page and footer area of
> pages.
> 
> I can't tell what went wrong, but expected autodate.tex should look like:

I found it out: gitlab was doing a shallow clone, and the previous tag was not
in the commits, so I modified the Gitlab config so it does a complete clone of
the repository instead.

The last output of the pipeline seems to have been correct, please check:
https://gitlab.com/linux-kernel/perfbook/-/jobs/3705185694/artifacts/browse


> 
> -----
> \date{February 1, 2023 \\ Commit: \texttt{v2022.09.25a-81-g4327c1f3809e}}
> \newcommand{\commityear}{2023}
> \newcommand{\commitid}{v2022.09.25a-81-g4327c1f3809e}
> \IfQqzBg{}{\setboolean{qqzbg}{false}}
> % tcolorbox version: 5.1
> \tcbsetforeverylayer{autoparskip}
> -----
> 
> It is not kept in the artifact, so I'm just guessing.
> I guess utilities/autodate.sh failed to see .git/ in the build directory
> and generated the following based on the build date instead:
> 
> -----
> \date{February 2, 2023  }
> \newcommand{\commityear}{2023}
> \newcommand{\commitid}{}
> \IfQqzBg{}{\setboolean{qqzbg}{false}}
> % tcolorbox version: 5.1
> \tcbsetforeverylayer{autoparskip}
> -----
> 
> Not a big deal, but can you look into this?
> 
> BTW, I just requested a permission for accessing your repo.

Let's put that on hold: I think it will be necessary to delete this repo and
import again from kernel.org if the pipeline don't work fine for next commits.

> 
>         Thanks, Akira
> 
> 

Thank you for reporting the issue!

Best regards,
Leo




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux